[ http://issues.apache.org/jira/browse/TOMAHAWK-706?page=comments#action_12437930 ] Werner Punz commented on TOMAHAWK-706: --------------------------------------
I dont think this is a real issue, onload is inherently evil and causes more problems than it solves. To my experience extensive body onload causes severe engine lockups in the ie 6 and 7 engine once the page becomes more complicated (been there done that, moved along). Also it breaks some components which uses the dojo onload infrastructure. If you need something which simulates this, use the dojo onload function which does resolve these problems in a somewhat better manner or use deferred javascript initialization via a small timeout of a handful of miliseconds. This causes the browser to render first and then executes the initialisation. In my experience this is the least problematic way to resolve those problems, it even works on a page which brings the IE to its limits without any engine lockups etc... > body onload does not exist > -------------------------- > > Key: TOMAHAWK-706 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-706 > Project: MyFaces Tomahawk > Issue Type: Improvement > Affects Versions: 1.1.3 > Reporter: Remo Liechti > Priority: Minor > > We are using myFaces 1.1.3. I have to do some javascript when the page is > loaded. But there is no onload attribute in <t:documentBody>. Since this > onload does not exist, no JavaScript can be executed on page load. This is > very bad, because parts of our application need to be able to do this. Can > you provide a workaround or a patch? Matthias Wessendorf [EMAIL PROTECTED] > knows about it, he told me to add it to jira. > Regards, > Remo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
