[WICKET-4111] addDomReadyEvent broken for IE

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.1
• Fix Version/s: 1.4.19, 1.5.2
• Component/s: wicket
• Labels: core event ie javascript
• Environment: IE 7-9
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Matthias Piepkorn
• Created: 06/Oct/11 07:32
• Updated: 20/Feb/12 12:45
• Resolved: 07/Oct/11 07:52

Description

Wicket.Event.addDomReadyEvent is broken in IE since 1.5.1. I identified WICKET-4080 as the cause of the problem: onreadystatechange with readyState="loaded" is sometimes fired before the document is fully loaded, causing scripts that reference DOM nodes to fail.

See http://msdn.microsoft.com/en-us/library/ms534359%28v=vs.85%29.aspx for the order of the readystate events.

The attached quickstart reproduces the issue (you may need to F5 a few times as it does not happen reliably). The actual JS error is:

SCRIPT5007: The property "onkeydown" has no value: The object is null or undefined
wicket-autocomplete-ver-1317728550188.js, Line 91 Character 9

Issue Links

• is broken by: WICKET-4080 domready events not always fired in IE
• is duplicated by: WICKET-4157 AjaxLazyLoadPanel not loading in IE 8 and 9 (not tested with IE 7)