[ http://issues.apache.org/jira/browse/TAPESTRY-788?page=comments#action_12367553 ]
Jesse Kuhnert commented on TAPESTRY-788: ---------------------------------------- The window.onload is undesirable for a lot of different reasons, one in particular that would affect me directly is that in the tacos ajax world there is no window.onload event for most request. The window gets loaded once and scritps are eval'd from responses. Is there a known way to push this render further down the pipeline, or is this just a limitation of the portlet spec? Perhaps we just need to fix what the DatePicker script is doing instead? That would be much preferred. Do you by any chance have IE's script debugger installed? (it's an optional component you can install with ms office cd's ) Perhaps there is a specific line or method that causes the error in question? I know for ajax type stuff at least that most IE related javascript calls have to be executed off the main rendering thread. This is usually solved by doing a setTimeout(function(), 50) which causes the scrips to be executed 50 ms later. I can try this if you like, or is this a global problem not just specific to DatePicker? > 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]
