Implementation for feature policy - fullscreen

third_party/WebKit/LayoutTests/http/tests/feature-policy/fullscreen-enabledforself-expected.txt

Index: third_party/WebKit/LayoutTests/http/tests/feature-policy/fullscreen-enabledforself-expected.txt
diff --git a/third_party/WebKit/LayoutTests/http/tests/feature-policy/fullscreen-enabledforself-expected.txt b/third_party/WebKit/LayoutTests/http/tests/feature-policy/fullscreen-enabledforself-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..2ac48783041ed9cb2e6138ee103851bc29e13c93
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/http/tests/feature-policy/fullscreen-enabledforself-expected.txt
@@ -0,0 +1,7 @@
+This is a testharness.js-based test.
+PASS Fullscreen enabled for self on URL: resources/feature-policy-fullscreen.html with allowfullscreen = false 
+PASS Fullscreen enabled for self on URL: http://localhost:8000/feature-policy/resources/feature-policy-fullscreen.html with allowfullscreen = false 
+FAIL Fullscreen enabled for self on URL: resources/feature-policy-fullscreen.html with allowfullscreen = true assert_false: expected false got true

[foolip, 2016/12/02 10:52:09]

To make it easier to see which assert this was that failed, you can add a short
description to each, like assert_false(data.enabled, 'enabled'). In general I
only bother when there are mulitple asserts of the same type though.

[lunalu1, 2016/12/02 19:22:06]

Done.

+FAIL Fullscreen enabled for self 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.
+