Adding chrome flag to disable implicit capture

content/public/common/content_features.cc

Index: content/public/common/content_features.cc
diff --git a/content/public/common/content_features.cc b/content/public/common/content_features.cc
index 5e28c3f52aca23b5c2eaf86e58803b7302c1285f..a803b730fddcc6e90967281c8817ed3beb4c47cb 100644
--- a/content/public/common/content_features.cc
+++ b/content/public/common/content_features.cc
@@ -108,6 +108,9 @@ const base::Feature kPassiveEventListenersDueToFling{
 // Pointer events support.
 const base::Feature kPointerEvents{"PointerEvent",
                                    base::FEATURE_DISABLED_BY_DEFAULT};
+// Pointer events no implicit capture

[Alexei Svitkine (slow), 2016/08/30 19:24:58]

Full sentence please.

[Navid Zolghadr, 2016/08/31 15:18:35]

Done.

+const base::Feature kPointerEventsNoImplicitCapture{
+    "PointerEventNoImplicitCapture", base::FEATURE_DISABLED_BY_DEFAULT};

[Alexei Svitkine (slow), 2016/08/30 19:24:58]

Would it make more sense to have the feature be "ImplicitCapture" and be enabled
by default?

[Navid Zolghadr, 2016/08/30 19:44:50]

I'm going to change the name to kPointerEventV1SpecCapturing to avoid the
confusion.

 
 // If Pepper 3D Image Chromium is allowed, this feature controls whether it is
 // enabled.