Re-enable feature policy layout tests after bug fix.

third_party/WebKit/LayoutTests/http/tests/feature-policy-experimental-features/vibrate-disabled-expected.txt

Index: third_party/WebKit/LayoutTests/http/tests/feature-policy-experimental-features/vibrate-disabled-expected.txt
diff --git a/third_party/WebKit/LayoutTests/http/tests/feature-policy-experimental-features/vibrate-disabled-expected.txt b/third_party/WebKit/LayoutTests/http/tests/feature-policy-experimental-features/vibrate-disabled-expected.txt
index ee1a21417a98cfff35a623f7736a1973728fcc3d..ae7093e985b6657a208398369e5099f4e410f6b8 100644
--- a/third_party/WebKit/LayoutTests/http/tests/feature-policy-experimental-features/vibrate-disabled-expected.txt
+++ b/third_party/WebKit/LayoutTests/http/tests/feature-policy-experimental-features/vibrate-disabled-expected.txt
@@ -1,17 +1,5 @@
- 
-
---------
-Frame: '<!--framePath //<!--frame0-->-->'
---------
-This is a testharness.js-based test.
-FAIL No iframe may call navigator.vibrate when disabled. assert_false: expected false got true
-Harness: the test ran to completion.
-
-
---------
-Frame: '<!--framePath //<!--frame1-->-->'
---------
 This is a testharness.js-based test.
-FAIL No iframe may call navigator.vibrate when disabled. assert_false: expected false got true
+FAIL Navigator.vibrate disabled on URL: resources/feature-policy-vibrate.html assert_false: navigator.vibrate(): expected false got true

[iclelland, 2017/05/18 19:36:12]

Does this mean that the test is currently failing? That vibrate is being allowed
everywhere, including cross-origin frames, even when disabled via feature
policy?

[lunalu1, 2017/05/19 20:54:08]

This is no longer the case.

+FAIL Navigator.vibrate disabled on URL: http://localhost:8000/feature-policy-experimental-features/resources/feature-policy-vibrate.html assert_false: navigator.vibrate(): expected false got true
 Harness: the test ran to completion.