New issue
Advanced search Search tips

Issue 664374 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Jul 5
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 1
Type: Feature

Blocked on:
issue 703703



Sign in to add a comment

Add layout tests for Feature Policy

Project Member Reported by iclell...@chromium.org, Nov 11 2016

Issue description

There should be layout tests for Feature Policy which demonstrate the correct enabling and disabling of features in various frame embedding scenarios, with different types of policies at different levels.

A comprehensive test suite will likely involve at least two levels of nesting, with three different origins. We should be able to use 127.0.0.1:8000, 127.0.0.2:8000 and localhost:8000 (127.0.0.1 is same-origin, localhost is used already in cross-origin tests, and hopefully 127.0.0.2 is also bound to the test web server)
 
Components: Blink>FeaturePolicy
Components: -Blink>SecurityFeature
Blocking: -623682
Labels: Feature-Policy-V2
We have tests now which test using Feature policy for specific features (fullscreen, vibrate). Testing FP itself will require an introspection interface, which is slated for FPV2
Blockedon: 703703
Status: Assigned (was: Started)
Status: Fixed (was: Assigned)
Tests have been added in several stages; LayoutTests/external/wpt/feature-policy/feature-policy-* contains the tests which use the introspection interface to test the policy mechanism itself.

Sign in to add a comment