Steps to Reproduce: ------------------- 1. Open the URL: "http://podcast.cdmamail.com/jquery/test.html" 2. Tap on the link "Core 4" Expected Outcome: ----------------- "0 tests of 69 failed" should be displayed. Actual Outcome: --------------- "7 tests of 69 failed" is displayed. 7 cases from the "core4 module: contents() (7, 5, 12)" is failing. Note: ----- Windows: Yes (7 tests of 69 failed) Safari: Yes (7 tests of 69 failed) Mozilla: Yes (5 tests of 69 failed)
Reproducible in: - QtWebKit trunk on Windows - WebKit nightly r55519 (Safari) on Windows - Chrome 4.0.249.89 (38071) on Windows
WebKit fires DOMContentLoaded before subframes load, which I think matches both Mozilla documentation and common sense. But these tests rely on subframe content being already available.
Created attachment 50159 [details] reduction
According to the HTML5 spec, the DOMContentLoaded event should not wait for subframes to load. See: http://dev.w3.org/html5/spec/Overview.html#the-end Notice that 8.2.6.4 is where DCL is fired and 8.2.6.6 is where we wait for subframes. This being said, a subframe may race the DCL event and win, but this should never be relied upon. I haven't looked at the tests, but perhaps they can be rewritten to use the window's load event instead of the DCL event. If you still believe this behavior to be incorrect, file a spec bug at http://www.w3.org/Bugs/Public/.