[
https://issues.apache.org/jira/browse/WICKET-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Dashorst reopened WICKET-4080:
--------------------------------------
> domready events not always fired in IE
> --------------------------------------
>
> Key: WICKET-4080
> URL: https://issues.apache.org/jira/browse/WICKET-4080
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.1
> Reporter: Emond Papegaaij
> Assignee: Martijn Dashorst
> Fix For: 1.5.2
>
> Attachments: dom-ready-ie-fix.patch
>
>
> The domready events for IE rely on a onreadystatechange to state 'complete'.
> Normally, this state should go from 'loading', to 'complete' to 'loaded'.
> However, IE does not always trigger events for all states. Why it skips
> certain events, I don't know, but it seems related to other content being
> loaded at the same time. Perhaps IE does not find the time to trigger the
> event and simply skips a step. If it skips 'loading' or 'loaded', there is no
> problem, but if it skips 'complete', the domready scripts will never run.
> I've never seen it skip more than one state, therefore I propose the attached
> patch, which also checks for 'loaded'.
> Although nothing has changed for a long time in wrt domready, this now is a
> serious issue when using the latest version of wiquery. The reason is that
> wiquery changes the order in which javascript files are added to head, and
> this different order causes IE to skip states far more frequently.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
