I recently re-wrote DOMReady.js and created a good solid test suite for it. I will make the time to look into your issue soon and figure out what's going on.
Sorry you're having issues :[ On Nov 11, 9:54 am, davepilbeam <[email protected]> wrote: > Hi, > > Using 1.3, been doing dev and now testing results in Explorer 6 (after > doing none since 1.2) and have what seems to be a big issue: > > On both the 1.3 pages listed below any call to $ and $$ fails on first > load - although both will work as expected after a reload.. the 1.2.5 > page behaves as you'd expect: > > Here's three basic test pages showing the simplest of PNG replacements > on domready: > > <a > href="http://www.parknet-hosting.co.uk/test/test125.html";>http://www.parknet-hosting.co.uk/test/test125.html</a> > - uses 1.2.5 - WORKS > as expected > > <a > href="http://www.parknet-hosting.co.uk/test/test13c.html";>http://www.parknet-hosting.co.uk/test/test13c.html</a> > - uses 1.3 > (compatibility) - FAILS at line 5 with 'undefined is null or not an > object' > > <a > href="http://www.parknet-hosting.co.uk/test/test13.html";>http://www.parknet-hosting.co.uk/test/test13.html</a> > - uses 1.3 - FAILS at > line 5 with 'undefined is null or not an object' > > Have done my research on explorer onload issues so I'm aware of 'wait > for Moottools 2.0', but surely if domready for ie6 works in 1.2.5, why > is it failing on the 1.3 versions here? > > (Tested on PC Ex 6 and emulators) > > Any insight would be appreciated, thanks.
