TYPO3 Core

Uploaded new patch, the old one wasn't quite right, so just ignore that one. Sorry about that!

Added a new patch which allows for arbitrary events.

Thanks Martin. I saw the duplicate load call and your comment whether it was necessary, and I am all for removing it. One should be enough.

More questions:

Should we change from document.onXXX to window.onXXX? onload and onunload belong to window not document, but others should stay with document.

OTOH the developer could simply use event listeners.

Not sure since both are valid and I am not a JS guy. I use it for Google Maps which requires the onload stuff to be in the body tag. So as long as I can still do that, I am good.
If they are different (couldn't find anything on Google about that), we could just add them as an option instead of including them all the time automatically.

Have a look how this is implemented in prototype.js event handlers ("_observeAndCache"):
http://dev.rubyonrails.org/browser/spinoffs/prototype/trunk/src/event.js#L61

My point was not how, but if we should use evebt listeners.

Okay :) IMHO we should use event listeners.

Fixed in TYPO3 4.1RC2

Committed to Trunk