Add command line switch to make pointer events enabled by default |
||
Issue descriptionChrome Version : 53.0.2756.0 We want a command-line switch which can be used to explicitly enable pointer events support. Technically you can do this today with --enable-blink-features=PointerEvent but this has two drawbacks: - Causes a yellow warning bar about untrusted "--enable-blink-features" switch - Can't then be disabled by the user in chrome://flags (the command line switch appears to take precedence over the chrome://flags entry). So I suggest a new switch which just makes the "default" value of the chrome://flags entry mean "enabled, something like --pointer-events-default-enabled.
,
Jun 22 2016
We don't need a new flag for this, instead use "--enable-features=PointerEvent". This already has the right set of properties: shows no warning bar, and can be disabled through chrome://flags too.
,
Jun 22 2016
Oh awesome, thanks Mustaq! I forgot we were using Chrome's '--enable-features' system here, not just Blink's '--enable-blink-features'. I can confirm that Chrome can be run with --enable-features=PointerEvent and have the desired properties (it shows as 'default' still in chrome://flags, and setting it to disabled indeed overrides what was specified on the command line). So we already have everything we need without having to add a new switch. |
||
►
Sign in to add a comment |
||
Comment 1 by mustaq@chromium.org
, Jun 21 2016