That appears to be a tangential issue (but one that also deserves merit -
Andrea, can you file a bug on it?).
Right now I'm leaning towards the domManip caching that landed a little
while ago as the possible culprit.
--John
On Mon, Jul 27, 2009 at 5:56 PM, Andrea Giammarchi <
andrea.giammar...@gmail.com> wrote:
> writing this it works properly:
>
> setTimeout(function(){
> $('#demo').click(function(){
> alert("This is right.");
> return false;
> });
> }, 1);
>
> so I guess the problem is in the "ready stack" ... I would fix direct
> execution once the onload is fired, avoiding cross checks over the queue and
> the rest.
>
>
>
>
>
> On Mon, Jul 27, 2009 at 10:45 PM, John Resig <jere...@gmail.com> wrote:
>
>> Weird... it really is on the 3rd time. I've got some ideas, I'll have to
>> dig in.
>>
>> --John
>>
>>
>>
>> On Mon, Jul 27, 2009 at 5:40 PM, mike.helgeson
>> <mike.helge...@gmail.com>wrote:
>>
>>>
>>> I have a small demo system, where you can edit and execute source code
>>> directly in the same page, and load and execute new demo pages using
>>> ajax. When attempting to upgrade to the 1.3.3 nightly (2009-07-25,
>>> rev. 6507). I noticed some problems with the script execution. I have
>>> put together two paired down sample pages.
>>>
>>> The first includes 1.3.2 and behaves correctly:
>>>
>>> http://jsbin.com/utita
>>>
>>> The second includes 1.3.3 (nightly) and fails for me on the 3rd
>>> execution:
>>>
>>> http://jsbin.com/ijuze
>>>
>>> Otherwise, the pages are identical.
>>>
>>> http://dev.jquery.com/ticket/4981
>>>
>>>
>>
>>
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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@googlegroups.com
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
