[ http://issues.apache.org/jira/browse/TAPESTRY-788?page=comments#action_12367548 ]
Jesse Kuhnert commented on TAPESTRY-788: ---------------------------------------- The initial reason for not wanting to apply this is that calling window.onload effectively obliterates any chance anyone else has of also capturing this event. I'm thinking about using this script to do it, http://dean.edwards.name/my/events.js, but am still unsure as it's such a potentially impactual change. > DatePicker doesn't work in a portlet. Initialization script is run before > window finishes loading. > -------------------------------------------------------------------------------------------------- > > Key: TAPESTRY-788 > URL: http://issues.apache.org/jira/browse/TAPESTRY-788 > Project: Tapestry > Type: Bug > Components: Portlet > Versions: 4.0 > Environment: Tapestry 4.0-beta-13 > Jetspeed 2 portal > Reporter: Raphael Jean > Assignee: Jesse Kuhnert > Fix For: 4.1 > > When using a DatePicker in a Tapestry portlet, IE displays an error message > during page loading and aborts: > "Internet Explorer cannot open the site http://localhost. Operation aborted" > It appears that this is caused by the initialization script of the DatePicker > component being run before the window finishes loading. The script is run > right before the portlet finishes rendering, which, in a portal environment, > is not necessarily the end of the page. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
