Repository navigation
Add pinch-zoom token to touch-action property? #68
Description
The touch-action property defines a number of tokens. Edge and Chrome also ship an additional pinch-zoom token (and I believe Firefox plans to as well /cc @staktrace). But it's not clear if this will ever make it into the W3C PointerEvents spec.
I think it's particularly important that we increase the visibility of this property (eg. document it on MDN for accessibility reasons. Many image carousels already use touch-action: pan-y when they probably should be using touch-action: pan-y pinch-zoom in order to avoid disabling zooming for vision impared users.
It'll be a little awkward to monkey patch it in, but is it OK if I submit a PR for this?
/cc @dtapuska @teddink @NavidZ @mustaqahmed
Activity
RByers commentedon Dec 20, 2016
Concretely I believe the grammar should change from:
auto | none | [ [ pan-x | pan-left | pan-right ] || [ pan-y | pan-up | pan-down ] ] | manipulationTo:
auto | none | [ [ pan-x | pan-left | pan-right ] || [ pan-y | pan-up | pan-down ] || pinch-zoom ] | manipulationI.e. pinch-zoom may optionally be specified along with the existing
panvalues (or by itself), but not in combination withauto,noneormanipulation.manipulationthen becomes a synonym forpan-x pan-y pinch-zoom.miketaylr commentedon Dec 20, 2016
Assuming this is something Gecko wants to ship eventually (or should otherwise be convinced to...), +1.
Add pinch-zoom into the touch-action css property.
Added 'pinch-zoom' to the 'touch-action' CSS property syntax (#28)
graouts commentedon Nov 13, 2018
Is it expected that
pinch-zoomwill make it to a Level 3 spec for Pointer Events at W3C?RByers commentedon Nov 13, 2018
No such plans unfortunately since it's out of scope for the W3C PEWG charter. But I believe all PE implementations actually implement it, so it may be required for web compatibility (to avoid creating accessibility issues).
NavidZ commentedon Nov 13, 2018
There is a test for it that we can add it to wpt as well under something like "de-facto" behaviors but not part of any specification.
RByers commentedon Nov 13, 2018
Oh yeah, it would be great to upstream our test! It doesn't need to be "defacto" - this IS specified in the compat spec, so you can add it https://github.com/web-platform-tests/wpt/tree/master/compat.