I've been following the body Onload discussion with interest. Not having had access to this solution when developing my application, I resorted to building a scheduler class:"Executive" which fielded the HTML-coded events from
<body onload="oExecutive.bodyOnload()" onUnload="oExecutive.bodyUnload()"> >From there, it's easy to imagine that the Executive class handles the dispatching of events to other Classes waiting for body Onload and Unload events. I have confidence that these events fire correctly in all browsers when the DOM is loaded and the images are still in-download-progress, providing a "fast" javascript initialization. This is the only event-markup on my page(s), and it seems a reasonable trade-off. So... I have a couple of questions: How much better is it to have a class to handle event dispatching Onload rather than hardcoding the event? Second - are there any (significant) unresolved cross-browser issues with the class FastInit ? Sam _______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
