On Jan 17, 2009, at 2:41 PM, MorningZ wrote:
I can't find the page where it's mentioned, but i am pretty sure that
"google.load" happens *asynchronously*, meaning that once in a while
maybe the jQuery library isn't loaded yet before $(document).ready
().... l
I'd suggest before doing or blaming anything to take the Google AJAX
Libraries out of the equation and use your own link to the jQuery
library, or... use this link
http://ajax.googleapis.com/ajax/libs/jquery/1.3.0/jquery.min.js
inside a script tag with the "src" set to that
Yes, that appears to be exactly what's going on. Thanks.
On Jan 17, 5:21 pm, Jonathan Lundell <jlund...@pobox.com> wrote:
On Jan 17, 2009, at 2:09 PM, Dave Methvin wrote:
Could you put together a page that fails? The .ready() method works
reliably for me.
http://lobitos.net/wx?loc=12345&fmt=wide
I added a button 'jqtest' that uses bind-on-ready to do the same
thing
that the 'raw' button does with onclick, and verified that I see
failures with both Mac Safari and FF3.
The failure doesn't happen 100% of the time; you might try other
zipcodes to avoid caching effects, which tend to 'fix' the problem.
Also, in Safari, at least, hitting a return in the URL field seems to
do a full reload, which is conducive to the failure.
