Automatic update from web-platform-tests Remove obsolete feature-policy sensor tests and rename to permissions-policy (#58469) * Remove obsolete feature-policy tests and rename to permissions-policy This PR cleans up remaining references to the deleted /feature-policy/ directory by: 1. Deleting obsolete sensor *-feature-policy* test files since their *-permissions-policy* equivalents already exist: - accelerometer/Accelerometer-*-by-feature-policy*.html (5 files + 3 headers) - gyroscope/Gyroscope-*-by-feature-policy*.html (5 files + 3 headers) - magnetometer/Magnetometer-*-by-feature-policy*.html (5 files + 3 headers) 2. Renaming generic-sensor-feature-policy-test.sub.js to generic-sensor-permissions-policy-test.sub.js and updating all imports 3. Updating generic-sensor-tests.js: - featurePolicyNames -> permissionsPolicyNames - Updated test description text 4. Updating generic-sensor-helpers.js: - featurePolicyNames -> permissionsPolicyNames 5. Updating all sensor-data.js files: - accelerometer/resources/sensor-data.js - ambient-light/resources/sensor-data.js - gyroscope/resources/sensor-data.js - magnetometer/resources/sensor-data.js - orientation-sensor/resources/sensor-data.js 6. Renaming client-hints files: - client-hints/accept-ch-stickiness/cross-origin-subresource-with-feature-policy.https.html -> cross-origin-subresource-with-permissions-policy.https.html (+ resources) - client-hints/accept-ch/feature-policy-navigation/ -> permissions-policy-navigation/ - client-hints/accept-ch/feature-policy.sub.https.html -> permissions-policy.sub.https.html 7. Renaming gamepad and permissions files: - gamepad/feature-policy-gamepad.html -> permissions-policy-gamepad.html - permissions/feature-policy-permissions-query.html -> permissions-policy-permissions-query.html - permissions/permissions-query-feature-policy-attribute.https.sub.html -> permissions-query-permissions-policy-attribute.https.sub.html 8. Deleting fenced-frame/client-hints-meta* files: These tests used <meta http-equiv="Feature-Policy"> which was deprecated. Permissions-Policy does NOT support http-equiv meta tags (only HTTP headers), so these tests cannot be migrated and are now obsolete. This follows up on PR #58327 which deleted the /feature-policy/ directory. * fixup -- wpt-commits: 0b8936dd0880c8251a4c247833327aaa6ae519de wpt-pr: 58469
75 lines
3.2 KiB
HTML
75 lines
3.2 KiB
HTML
<!DOCTYPE html>
|
|
<body>
|
|
<script src=/resources/testharness.js></script>
|
|
<script src=/resources/testharnessreport.js></script>
|
|
<script src=/permissions-policy/resources/permissions-policy.js></script>
|
|
<!-- Permissions-Policy: fullscreen=cross_origin https://www.example.com; -->
|
|
<script>
|
|
'use strict';
|
|
var same_origin = 'https://{{domains[]}}:{{ports[https][0]}}';
|
|
var cross_origin = 'https://{{domains[www]}}:{{ports[https][0]}}';
|
|
var cross_origin1 = 'https://{{domains[www1]}}:{{ports[https][0]}}';
|
|
var same_origin_src = '/permissions-policy/resources/permissions-policy-allowedfeatures.html';
|
|
var cross_origin_src = cross_origin + same_origin_src;
|
|
var cross_origin_src1 = cross_origin1 + same_origin_src;
|
|
var header_policy = `Permissions-Policy: fullscreen=(self "${cross_origin}" "https://www.example.com"`;
|
|
|
|
// Test that fullscreen's allowlist is [same_origin, cross_origin, 'https://www.example.com']
|
|
test(function() {
|
|
assert_array_equals(
|
|
document.permissionsPolicy.getAllowlistForFeature('fullscreen'),
|
|
[cross_origin, 'https://www.example.com'].sort());
|
|
}, header_policy + ' -- test allowlist is [cross_origin, https://www.example.com]');
|
|
|
|
// Test that fullscreen is everywhere.
|
|
test_disallowed_feature_for_subframe(
|
|
header_policy + ' -- test fullscreen is disallowed on same-origin subframe',
|
|
'fullscreen',
|
|
same_origin_src);
|
|
test_disallowed_feature_for_subframe(
|
|
header_policy + ' -- test fullscreen is disallowed on cross-origin ' + cross_origin_src + ' subframe',
|
|
'fullscreen',
|
|
cross_origin_src);
|
|
test_disallowed_feature_for_subframe(
|
|
header_policy + ' -- test fullscreen is disallowed on cross-origin ' + cross_origin_src1 + ' subframe',
|
|
'fullscreen',
|
|
cross_origin_src1);
|
|
|
|
// dynamically update sub frame's container policy to none
|
|
var disallow = "fullscreen 'none';"
|
|
test_disallowed_feature_for_subframe(
|
|
header_policy + ', iframe.allow = ' + disallow + ' -- test fullscreen is disallowed on same-origin subframe',
|
|
'fullscreen',
|
|
same_origin_src,
|
|
disallow);
|
|
test_disallowed_feature_for_subframe(
|
|
header_policy + 'iframe.allow = ' + disallow + ' -- test fullscreen is disallowed on specific cross-origin subframe',
|
|
'fullscreen',
|
|
cross_origin_src,
|
|
disallow);
|
|
test_disallowed_feature_for_subframe(
|
|
header_policy + 'iframe.allow = ' + disallow + ' -- test fullscreen is disallowed on another cross-origin subframe',
|
|
'fullscreen',
|
|
cross_origin_src1,
|
|
disallow);
|
|
|
|
// dynamically update sub frame's container policy to cross_origin
|
|
var allow = "fullscreen " + cross_origin;
|
|
test_disallowed_feature_for_subframe(
|
|
header_policy + ', iframe.allow = ' + allow + ' -- test fullscreen is disallowed on same-origin subframe',
|
|
'fullscreen',
|
|
same_origin_src,
|
|
allow);
|
|
test_disallowed_feature_for_subframe(
|
|
header_policy + 'iframe.allow = ' + allow + ' -- test fullscreen is disallowed on specific cross-origin subframe',
|
|
'fullscreen',
|
|
cross_origin_src,
|
|
allow);
|
|
test_disallowed_feature_for_subframe(
|
|
header_policy + 'iframe.allow = ' + allow + ' -- test fullscreen is disallowed on another cross-origin subframe',
|
|
'fullscreen',
|
|
cross_origin_src1,
|
|
allow);
|
|
</script>
|
|
</body>
|