WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
112293
Layout Test http/tests/security/cross-frame-access-port-explicit-domain.html is flaky
https://bugs.webkit.org/show_bug.cgi?id=112293
Summary
Layout Test http/tests/security/cross-frame-access-port-explicit-domain.html ...
James Robinson
Reported
2013-03-13 14:48:17 PDT
The following layout test is flaky on all platforms: http/tests/security/cross-frame-access-port-explicit-domain.html See history:
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=fast%2FinnerHTML%2FinnerHTML-iframe.html
Here's a failure diff: --- /b/build/slave/WebKit_Mac10_7/build/layout-test-results/http/tests/security/cross-frame-access-port-explicit-domain-expected.txt +++ /b/build/slave/WebKit_Mac10_7/build/layout-test-results/http/tests/security/cross-frame-access-port-explicit-domain-actual.txt @@ -1,12 +1,10 @@ This test currently fails because we check the port and protocol even if document.domain is explicitly set (
rdar://problem/5366437
). -PASS: Cross frame access to a different port, after explicitly setting document.domain, was allowed! +Fail: Cross frame access to a different port, after explicitly setting document.domain, was denied. -------- Frame: 'aFrame' -------- -PASS: Cross frame access to a different port, after explicitly setting document.domain, was allowed! - Inner iframe with explicit document.domain set. Seems kind of bad, but I don't know much about this.
Attachments
Add attachment
proposed patch, testcase, etc.
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