NEW 184362
Layout Test imported/w3c/web-platform-tests/FileAPI/url/sandboxed-iframe.html is failing
https://bugs.webkit.org/show_bug.cgi?id=184362
Summary Layout Test imported/w3c/web-platform-tests/FileAPI/url/sandboxed-iframe.html...
Ryan Haddad
Reported 2018-04-06 12:00:40 PDT
The following layout test is failing on macOS imported/w3c/web-platform-tests/FileAPI/url/sandboxed-iframe.html Probable cause: This test is failing since it was imported in https://trac.webkit.org/changeset/230330/webkit#file143 Flakiness Dashboard: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fw3c%2Fweb-platform-tests%2FFileAPI%2Furl%2Fsandboxed-iframe.html --- /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/FileAPI/url/sandboxed-iframe-expected.txt +++ /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/FileAPI/url/sandboxed-iframe-actual.txt @@ -1,4 +1,5 @@ CONSOLE MESSAGE: line 1714: SecurityError: Sandbox access violation: Blocked a frame at "http://localhost:8800" from accessing a frame at "null". The frame being accessed is sandboxed and lacks the "allow-same-origin" flag. +CONSOLE MESSAGE: line 67: XMLHttpRequest cannot load blob:null/7c9635f7-5ee0-4a9e-9924-aba22c05aee5. Cross origin requests are only supported for HTTP. FAIL FileAPI Test: Verify behavior of Blob URL in unique origins SecurityError: Sandbox access violation: Blocked a frame at "http://localhost:8800" from accessing a frame at "null". The frame being accessed is sandboxed and lacks the "allow-same-origin" flag.
Attachments
Ryan Haddad
Comment 1 2018-04-06 12:08:02 PDT
Removed the pass expectation for mac-wk2 in https://trac.webkit.org/r230343 Not sure if this just needs a rebaseline.
Brendan McLoughlin
Comment 2 2018-04-06 12:31:33 PDT
Removing the pass expectation looks like the correct fix. I don't think a rebaseline will help since the id in the blob url changes with each run.
Note You need to log in before you can comment on or make changes to this bug.