Add switch to disable WebVR gesture requirement

third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in

Index: third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in
diff --git a/third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in b/third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in
index a1a27b1ca3a268e5cd8b0c9b2d53072913fbbc50..bc5f06f551fe014a0396a6a745737c83fa9fdc60 100644
--- a/third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in
+++ b/third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in
@@ -250,6 +250,7 @@ WebGLDraftExtensions status=experimental
 WebGLImageChromium
 WebUSB status=experimental, origin_trial_feature_name=WebUSB
 WebVR origin_trial_feature_name=WebVR
+WebVrRequiresUserGesture status=stable

[haraken, 2016/12/01 01:19:17]

Oh, you need to add "status=stable" to make your CL work... Hmm.

Feature flags with "status=stable" are expected to be removed once the features
are fully stabilized. In other words, we shouldn't keep the feature flags just
for testing purposes.

Maybe we should ask API owners how to handle this situation.

+Rick

[kinuko, 2016/12/01 02:22:02]

If the flag is not about feature stability but for testing could we use an
inverted flag name (e.g. WebVrAllowedWithoutUserGesture) with no status values
to make the intention / expected default behavior clearer?  Would be also nice
to have a short comment to note that the flag is for testing purpose.

 WebVTTRegions status=experimental
 V8BasedStructuredClone status=stable
 V8IdleTasks
@@ -270,4 +271,4 @@ LazyParseCSS status=experimental
 ParseHTMLOnMainThread status=test
 SendBeaconThrowForBlobWithNonSimpleType status=experimental
 PerformanceNavigationTiming2 status=test
-BackgroundVideoTrackOptimization status=stable
+BackgroundVideoTrackOptimization status=stable