IMHO, "contentloaded" should be fired once, when the DOM of the  
initial page is completely loaded and parsed by the browser.

Loading in stuff via Ajax shouldn't trigger this event.

YMMV, but you can add a global ajax responder and fire a  
"fragmentloaded" (or so) custom event, and oberve that, or just use  
text/javascript returns (note that this would well be something that  
we consider for inclusion in the library!).

I think making contentloaded too magic breaks POLS.


Am 31.08.2007 um 17:25 schrieb Jeff Watkins:

> On Aug 31, 2007, at 12:34 AM, Andrew Dupont wrote:
>> Jeff, my suggestion is to write your own Event.onReady function (or
>> something like it) that wraps around the 1.6 event code.
> Yeah, that's kind of what I figured. But since it's got to be a
> pretty common situation, I thought it might deserve a solution in the
> library.
> >

You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at

Reply via email to