WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
91376
[Qt] http/tests/security/sandboxed-iframe-modify-self.html flaky
https://bugs.webkit.org/show_bug.cgi?id=91376
Summary
[Qt] http/tests/security/sandboxed-iframe-modify-self.html flaky
Zoltan Arvai
Reported
2012-07-16 04:55:57 PDT
Test is flaky on Qt. --- /ramdisk/qt-linux-release/build/layout-test-results/http/tests/security/sandboxed-iframe-modify-self-expected.txt +++ /ramdisk/qt-linux-release/build/layout-test-results/http/tests/security/sandboxed-iframe-modify-self-actual.txt @@ -1,3 +1,5 @@ +CONSOLE MESSAGE: Unsafe JavaScript attempt to initiate a navigation change for frame with URL
http://127.0.0.1:8000/security/sandboxed-iframe-form-top.html
from frame with URL
http://127.0.0.1:8000/security/resources/sandboxed-iframe-form-top.html
. + CONSOLE MESSAGE: Unsafe JavaScript attempt to access frame with URL
http://127.0.0.1:8000/security/sandboxed-iframe-modify-self.html
from frame with URL
http://127.0.0.1:8000/security/resources/sandboxed-iframe-modify-self.html
. Domains, protocols and ports must match. This is a "sanity" test case to verify that a sandboxed frame cannot break out of its sandbox by modifying its own sandbox attribute. Two attempts are made:
Attachments
Add attachment
proposed patch, testcase, etc.
Zoltan Arvai
Comment 1
2012-07-16 05:55:33 PDT
Added to TestExpections in
r122718
: <
http://trac.webkit.org/changeset/122718
>
Jocelyn Turcotte
Comment 2
2014-02-03 03:21:43 PST
=== Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at
https://bugreports.qt-project.org
and add a link to this issue. See
http://qt-project.org/wiki/ReportingBugsInQt
for additional guidelines.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug