Also is there any validity in the concern that without proper checks
the window.onload trigger could happen in the middle of executing the
"contentloaded" observers (esp. in IE when you are emulating a
"contentloaded" event)?
Do you have a way to ensure proper "first in first out order" or event
This is probably the most glaring flaw in RC0: any event types that
are not part of the DOM L2 Events spec, but are nonetheless honored by
one or more browsers, are handled incorrectly by Prototype as custom
events.
We've got to figure out a way around this, even if it means we create
a whitelist