In my code this was an issue because I had a forl oop iterating over
the DOMContentLoaded observers and,
I had a case where the loop would be half through and the window
onload would fire,
calling code that hadent yet been inited in the DOMContentLoaded

Becuase 1.6 uses a real event to callback maybe it wont have that same
issue and will behave properly.

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