Mirrors/servo
1
0
Fork 0
mirror of https://github.com/servo/servo.git synced 2025-08-17 19:35:33 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update web-platform-tests to revision 122a4672fa0dc554a6e7528fa3487fd907c792ee

Browse source
This commit is contained in:
WPT Sync Bot 2019-03-23 21:54:52 -04:00
parent fb1123495f
commit 93d826f7ba
301 changed files with 4775 additions and 1769 deletions
Download patch file Download diff file Expand all files Collapse all files

1
tests/wpt/web-platform-tests/content-security-policy/generic/no-default-src.sub.html
View file

@ -2,6 +2,7 @@
<html>
<head>
<title>no default src doesn't behave exactly like *</title>
<meta name="timeout" content="long">
<script src='/resources/testharness.js'></script>
<script src='/resources/testharnessreport.js'></script>
<script src="../support/alertAssert.sub.js?alerts=[]"> </script>

3
tests/wpt/web-platform-tests/content-security-policy/reporting/report-cross-origin-no-cookies.sub.html
View file

@ -1,9 +1,10 @@
<!DOCTYPE html>
<html>
<head>
<title>Cookies are not sent on cross origin violation reports</title>
<meta name="timeout" content="long">
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<title>Cookies are not sent on cross origin violation reports</title>
<!-- CSP headers
Content-Security-Policy: script-src 'unsafe-inline' 'self'; img-src 'none'; report-uri http://{{domains[www1]}}:{{ports[http][0]}}/content-security-policy/support/report.py?op=put&reportID=$id
-->

3
tests/wpt/web-platform-tests/content-security-policy/reporting/report-only-in-meta.sub.html
View file

@ -1,9 +1,10 @@
<!DOCTYPE html>
<html>
<head>
<title>Report-only policy not allowed in meta tag</title>
<meta name="timeout" content="long">
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<title>Report-only policy not allowed in meta tag</title>
<!-- CSP headers
Content-Security-Policy: script-src 'unsafe-inline' 'self'
-->

1
tests/wpt/web-platform-tests/content-security-policy/style-src/style-src-multiple-policies-multiple-hashing-algorithms.html
View file

@ -2,6 +2,7 @@
<html>
<head>
<title>Multiple policies with different hashing algorithms still work.</title>
<meta name="timeout" content="long">
<script src='/resources/testharness.js'></script>
<script src='/resources/testharnessreport.js'></script>
</head>

8
tests/wpt/web-platform-tests/content-security-policy/support/checkReport.sub.js
View file

@ -41,7 +41,13 @@
}
}
var timeout = document.querySelector("meta[name=timeout][content=long]") ? 50 : 5;
// There is no real way to test (in this particular layer) that a CSP report
// has *not* been sent, at least not without some major reworks and
// involvement from all the platform participants. So the current "solution"
// is to wait for some reasonable amount of time and if no report has been
// received to conclude that no report has been generated. These timeouts must
// not exceed the test timeouts set by vendors otherwise the test would fail.
var timeout = document.querySelector("meta[name=timeout][content=long]") ? 25 : 5;
var reportLocation = location.protocol + "//" + location.host + "/content-security-policy/support/report.py?op=retrieve_report&timeout=" + timeout + "&reportID=" + reportID;
if (testName == "") testName = "Violation report status OK.";