Bug 125487

Summary: Test results of postMessage-clone-port-error.html are broken
Product: WebKit Reporter: Michał Poteralski <m.poteralski>
Component: WebCore JavaScriptAssignee: Michał Poteralski <m.poteralski>
Status: RESOLVED FIXED    
Severity: Normal CC: ap, commit-queue, g.czajkowski
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch no 1
none
Patch none

Michał Poteralski
Reported 2013-12-10 01:38:15 PST
Order of: LayoutTests/fast/dom/Window/postMessage-clone-port-error.html is broken. Currently is: > LayoutTests/fast/dom/Window/postMessage-clone-port-error-expected.txt:4 > +PASS successfullyParsed is true > + > +TEST COMPLETE > +PASS exName is "DataCloneError" TEST COMPLETE should be the last line.
Attachments
Patch no 1 (1.92 KB, patch)
2013-12-10 12:35 PST, Michał Poteralski
no flags
Patch (2.88 KB, patch)
2013-12-11 00:44 PST, Michał Poteralski
no flags
Alexey Proskuryakov
Comment 1 2013-12-10 10:01:53 PST
The easiest way to address this is probably to move the test from onload to being run duting parsing. Alternatively jsTesIsAsync variable could be set, and finishJSTest() called when done.
Michał Poteralski
Comment 2 2013-12-10 12:35:56 PST
Created attachment 218892 [details] Patch no 1
Alexey Proskuryakov
Comment 3 2013-12-10 14:06:07 PST
Comment on attachment 218892 [details] Patch no 1 View in context: https://bugs.webkit.org/attachment.cgi?id=218892&action=review > LayoutTests/fast/dom/Window/postMessage-clone-port-error.html:7 > +<div id='container'></div> This doesn't seem relevant. Possibly this came from a test that did need it?
Michał Poteralski
Comment 4 2013-12-11 00:44:02 PST
WebKit Commit Bot
Comment 5 2013-12-11 02:48:04 PST
Comment on attachment 218936 [details] Patch Clearing flags on attachment: 218936 Committed r160418: <http://trac.webkit.org/changeset/160418>
WebKit Commit Bot
Comment 6 2013-12-11 02:48:06 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.