cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28102] - [PATCH] Client-side: window.onload handler clobbered by <body onload="...">
Date Thu, 01 Apr 2004 17:44:34 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28102>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28102

[PATCH] Client-side: window.onload handler clobbered by <body onload="...">





------- Additional Comments From ml@wrinkledog.com  2004-04-01 17:44 -------
I don't see how it would... the current XSLT does the right thing with @onload, which includes
inserting 
the call to forms_onload().  The problem isn't with transforming <body onload="..">
in the source 
document, it's with what happens if the window.onload property is set when the browser encounters

the <body> tag.

This is a pain in the butt.  We should change forms_lib.js to use the DOM Level 2 event model
(i.e., 
addEventListener(), and get Matt Kruse to do the same if necessary for his stuff that we redistribute.
 
That way it'll work for people who are using the DOM Level 0 style (like I was, but won't
anymore...).  
Meanwhile, I'll switch my client-side js to use addEventListener(), then I can lose this local
mod to 
forms_lib.js...

Mime
View raw message