This html:
Lorem ipsum dolor sit amet.
This jQuery:
$(document).ready(function(){
alert($('#demo').contents().filter('[nodeType = 3]').length);
alert($('#demo').contents().filter('[nodeType=3]').length);
});
both alerts are 1 in 1.2.6, 0 in 1.3_b1
Thanks, Marion
--~--~-~--~~
I just attached a patch for ticket http://dev.jquery.com/ticket/3649 to fix
getting and setting tabindex in IE. I'm hoping the patch can be reviewed
and committed for 1.3.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Grou
Hi John,
If I change my time to 1 then both demos do work the same. But I still
think this is a bug in 1.3_b1.
I queue up 3 animations, and use tail recursion so they happen one at
a time. In 1.3_b1 the 2nd and 3rd animations happen simultaneously,
but not in 1.2.6. Here's the code:
(function (
The YUI compressor is optimal, except that it adds curly braces even
for one-statement blocks.
That's a wasted byte :)
--
Ariel Flesler
http://flesler.blogspot.com
On Jan 4, 3:46 pm, Cloudream wrote:
> Yes, I noticed you use YUICompressor in makefile just now :D
>
> On Jan 5, 1:22 am, "John Re
Yes, I noticed you use YUICompressor in makefile just now :D
On Jan 5, 1:22 am, "John Resig" wrote:
> Good catch, fixed.
>
> By the way - this bug was in response to the patch that I landed
> earlier which moves us from using JSMin to
> YUIMin:http://dev.jquery.com/changeset/6027
>
> --John
>
>
Good catch, fixed.
By the way - this bug was in response to the patch that I landed
earlier which moves us from using JSMin to YUIMin:
http://dev.jquery.com/changeset/6027
--John
On Sun, Jan 4, 2009 at 12:04 PM, Cloudream wrote:
>
> http://dev.jquery.com/ticket/3779
>
> http://dev.jquery.com
This may help you hunt down the issue, but one change that was made
was that if a time of 0 is passed in to an animation then it happens
instantly (no delay, no asynchronous behavior). Thus you'll probably
want to take that into account when doing an animation like that.
I have a feeling that if
I boiled it down as much as I could. Test case is here:
http://newlevant.com/marion/jqueryplugins/concentrationBug/
Calling animate like so:
animate({opacity: 1.0}, flip.time, function () { ... });
And if flip.time is 0, subsequent calls don't wait for the animation
to finish before calling the
http://dev.jquery.com/ticket/3779
http://dev.jquery.com/attachment/ticket/3779/build.diff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-dev@go
Here it is: http://dev.jquery.com/ticket/3778
On Jan 4, 3:40 pm, "John Resig" wrote:
> I will agree that neither of those are ideal - but thankfully they're
> both sufficiently obscure enough that they won't cause immediate
> problems.
>
> Could you file a bug on them?http://dev.jquery.com/
>
>
I will agree that neither of those are ideal - but thankfully they're
both sufficiently obscure enough that they won't cause immediate
problems.
Could you file a bug on them?
http://dev.jquery.com/
Thanks!
--John
On Sun, Jan 4, 2009 at 9:31 AM, Balazs Endresz wrote:
>
> After some more test
After some more testing there seems to be some issues with this
approach as it fails if you have a selector like this:
input[name=".types["]
If the value contains a dot and an opening bracket then the class
selector regex will match the string after the dot.
Also it won't match .foo in this expre
12 matches
Mail list logo
