Bug 14944 - Running http/tests/security after fast/dom/Window causes failures in cross-site scripting tests
Summary: Running http/tests/security after fast/dom/Window causes failures in cross-si...
Status: RESOLVED DUPLICATE of bug 15220
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 523.x (Safari 3)
Hardware: Macintosh OS X 10.4
: P2 Normal
Assignee: Nobody
Keywords: LayoutTestFailure
Depends on:
Reported: 2007-08-11 15:24 PDT by David Kilzer (:ddkilzer)
Modified: 2007-09-18 08:49 PDT (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description David Kilzer (:ddkilzer) 2007-08-11 15:24:21 PDT
Running tests in http/tests/security after tests in fast/dom/Window causes failures in various cross-site scripting (xss-*) tests.  (Is some variable in DumpRenderTree not getting reset properly?)

1. Run layout tests thusly:
$ ./WebKitTools/Scripts/run-webkit-tests --debug fast/dom/Window http/tests/security
2. Wait for results.

Most of the xss-* tests fail because '[object Object]' gets inserted into the frame name like this:

-ALERT: PASS: window.name should be '<!--framePath //<!--frame0-->-->' and is.
+ALERT: PASS: window.name should be '<!--framePath /[object Object]/<!--frame0-->-->' and is.

The fast/dom/Window/window-resize.html test also fails on my PB G4 (independent of running the layout tests to reproduce this bug).  I don't think that affects this issue, though.
Comment 1 David Kilzer (:ddkilzer) 2007-09-18 08:49:22 PDT

*** This bug has been marked as a duplicate of 15220 ***