Yeah, this was intentional - since Safari now has a decent DOM ready technique, we switched to that. To be clear: It's not possible to run the ready event if jQuery is dynamically loaded in any browser that uses .addEventListener( "DOMContentLoaded" ... ).
Well, at least, can't detect it using that technique, alone. Both Safari and Opera have the readyState property which can be used to spot DOM ready loading but Firefox only just received that property in 3.5 (if memory serves me correctly). If an alternative technique can be spotted which works in all browsers then I would definitely be interested. --John On Tue, Jun 30, 2009 at 8:49 PM, Steven Parkes<smpar...@smparkes.net> wrote: > > I dynamically load jquery into my page and the change that happened at/ > round Ticket 2614 (http://dev.jquery.com/ticket/2614) / rev 5970 (or, > in other words, between 1.2.6 and 1.3.2) had, at least for me, a > pretty adverse effect. > > Looks like now if jquery is ever loaded after the doc readystate is > loaded/complete, jquery is never going to be ready. Looks like ticket > was to clean up the CSS stuff, but was this other behavior change > intentional? I'd really like to be able to load jquery dynamically and > that seems impossible for me at the moment on Safari. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
