This project is archived and is in readonly mode.

#351 ✓resolved

Safari 3 : Dom not ready on domready

Reported by cyberfish | September 2nd, 2008 @ 02:52 PM | in 1.2.1

I may say something totally wrong but while testing ondomready event on quite heavy DOM structure I needed to change the following lines :

switch ({
		case 'webkit': (function(){
			(['loaded', 'complete'].contains(document.readyState)) ? domready() : arguments.callee.delay(50);
		})(); break;


case 'webkit': (function(){
			var stopValue=(Browser.Engine.version==420) ? ['complete'] : ['loaded', 'complete'];
			(stopValue.contains(document.readyState)) ? domready() : arguments.callee.delay(50);
		})(); break;

I don't know if this is the correct way to do so but it works for me and might be useful for others.

Please accept my apologies if this have nothing to do here.

Mootools is great work. Thank you for creating it.

Best regards

Comments and changes to this ticket

  • Tom Occhino

    Tom Occhino October 6th, 2008 @ 06:39 AM

    • Assigned user changed from “Yuffster” to “Valerio”
    • State changed from “new” to “resolved”
    • Milestone changed from 2.0 to 1.2.1

    fixed for 1.2.1

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Shared Ticket Bins

People watching this ticket

Referenced by