Index: third_party/WebKit/LayoutTests/http/tests/feature-policy/fullscreen-disabled-expected.txt |
diff --git a/third_party/WebKit/LayoutTests/http/tests/feature-policy/fullscreen-disabled-expected.txt b/third_party/WebKit/LayoutTests/http/tests/feature-policy/fullscreen-disabled-expected.txt |
new file mode 100644 |
index 0000000000000000000000000000000000000000..d2d93a494ad4b44d20cd698d2bd66cd60dde7ec5 |
--- /dev/null |
+++ b/third_party/WebKit/LayoutTests/http/tests/feature-policy/fullscreen-disabled-expected.txt |
@@ -0,0 +1,7 @@ |
+This is a testharness.js-based test. |
+PASS Fullscreen disabled on URL: resources/feature-policy-fullscreen.html with allowfullscreen = false |
+PASS Fullscreen disabled on URL: http://localhost:8000/feature-policy/resources/feature-policy-fullscreen.html with allowfullscreen = false |
+FAIL Fullscreen disabled on URL: resources/feature-policy-fullscreen.html with allowfullscreen = true assert_false: expected false got true |
foolip
2016/12/02 10:52:09
Should it fail?
lunalu1
2016/12/02 19:22:06
Yes, without the feature policy runtime flag turne
|
+FAIL Fullscreen disabled on URL: http://localhost:8000/feature-policy/resources/feature-policy-fullscreen.html with allowfullscreen = true assert_false: expected false got true |
+Harness: the test ran to completion. |
+ |