- From: Bo Cupp via GitHub <sysbot+gh@w3.org>
- Date: Sun, 15 Sep 2019 04:26:38 +0000
- To: public-pointer-events@w3.org
Regarding a more generic proposal in response to the WG feedback, @gked and I played with some syntax and arrived at the same proposal by @NekR above. pointer-action: pen(none) touch(pan zoom); We like the future-proofing of this proposal. Here are some additional specifics that I imagined were implied by it: The type should parse correctly for any string that syntactically could be a valid future pointer-type. The property should also parse correctly for any string that syntactically could be a valid future action. For example, `pointer-action: dial(rotate);` could be a valid future pointer-action value and should be allowed by user agents. The user agent is not obligated to recognize and fulfill any particular action, however it is obligated to limit the actions possible to those that have been explicitly put into the list. For example, `pointer-action: pen(none);`, means that touch is unaffected as it isn't explicitly listed. It also means that if `gaze(pan)` is ever supported that the user agent should consider it still enabled. If the author wants to ensure no actions are possible (the author always wants to see the events), `pointer-action: all(none);` can be specified. The `touch-action` property would become deprecated and equivalent to `pointer-action: all(touch-action values here);` or `pointer-action: touch(values here) pen(values here);` -- GitHub Notification of comment by BoCupp-Microsoft Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/203#issuecomment-531533537 using your GitHub account
Received on Sunday, 15 September 2019 04:26:40 UTC