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 [EMAIL PROTECTED] 2004-04-01 00:27 ------- Apparently so, but I believe something I wrote in my last comment was inconsistent with my opening comment for this bug. @onload does set window.onload, but the only way that could trash anything would be if I set window.onload _before_ the <body> tag. I looked at the case that may have been where I discovered that, and that is indeed what I'm doing (external <script> as child of <head>). So... I would still like for form-lib.js not to trash that window.onload; however, if I _had_ set window.onload after the <body> tag (as I suggested in me previous comment), it would have been a case of _me_ clobbering the onload handler set by @onload! Then I would have had some subtler failure with the CForms client-side help not working right, and there's nothing that can be done in forms-lib.js to prevent that.
