Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>This problem is either in a IE6-only part of jQuery, or in a general part of jQuery that is lacking IE6 especific code (as noted in the comments). Either way, it's still a bug in jQuery that needs addressing. about:blank You'll either have to <a href="http://dev.jquery.com/browser/" rel="nofollow noreferrer">dig yourself into jQuery</a> or <a href="http://dev.jquery.com/report/" rel="nofollow noreferrer">file a bug ticket</a>. If you manage to fix it, don't forget to attach a diff to the bugtracker, so the project gets a little bit better. ;) </p> <p>If I get some spare time, I'll try to help you with this.</p> <h2>Edit</h2> <p>Ok, so the problem seems unsurmountable.</p> <p>The leak you are facing is an IE 6 SP 0 only problem, a leak caused by IE's approach to DOM. Doesn't matter what JS framework you use, it refuses to work correctly.</p> <p>So, your current options are:</p> <ul> <li><a href="http://www.imdb.com/title/tt1060277/quotes" rel="nofollow noreferrer">Die trying</a> to get your users to upgrade IE 6 to a newer version/Service Pack,</li> <li>Die (as in leak) in IE (loosing customers) or</li> <li>Die trying to work on IE.</li> </ul> <p>But that doesn't necesarily means you can't work this out. What about just trying to side pass the wole thing?</p> <p>Show every non IE 6 SP 0 user the jQuery datepicker, and only IE 6 SP 0 another more resilient (and probably basic) datepicker with IE's <a href="http://msdn.microsoft.com/en-us/library/ms537512(VS.85).aspx" rel="nofollow noreferrer">conditional comments</a>. This way you can keep the eye candy/functionality in your software, and allow IE 6 users to have the same basic functionality.</p> <p>It might not be such a clean option, but you'd still be able to use what you want, and IE6 will still be able to work without leaking. </p> <p>The <em>only</em> problem will be that you'll have a bigger burden, by having to degug two distinct datepickers. But you'll have to debug IE 6 anyway so, it may be your best bet at the moment.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload