John Resig wrote:
> Hi Everyone -
>
> The bug fix release for 1.1 is now ready for all to use. There were a
> lot of weird behaviors that were discovered post-1.1 that needed to be
> remedied sooner, rather than later. If you were having any
> difficulties with the 1.1 release, please try this new release to see
> if your problems were solved.
>
> It is highly recommended that you upgrade.
>
> As always, if you have any questions or concerns with new release,
> please feel free to discuss it here. If you think you've spotted a
> bug, please add it to the bug tracker
> (http://jquery.com/dev/bugs/new/)
Thank you very much for the fast update. Regarding the kind of bugs and
their impact I have the impression that the 1.1 release has been pushed
out a little too early (ok, it was that birthday thing).
The whole process is a bit frustating again. Now I have updated to 1.1.1
and again other simple things do not work anymore. The following worked
fine with 1.1:
$('<li><a href="#">Change
location</a></li>').prependTo('#nav').find('a').bind('click', function() {
var close = $('span', this); // same with $(this).find('span');
console.log( close[0]); // it's the <a> and not a <span> element
return false;
});
I wonder if this is the desired behavior with the "not destructive"
feature? Shouldn't $('span', this)[0] return undefined, e.g. shouldn't
the result be an empty array if there's no such element? Now it is
impossible to check for an element and append that if it's not present...
http://jquery.com/dev/bugs/bug/861/
-- Klaus
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
