Fix the touch-action processing model for zoom scenarios #24
Conversation
It's incorrect to consider the touch-action values only up to the nearest ancestor that supports ANY default touch behavior. Eg. in Edge you can disable double-tap to zoom across an entire page (including any iframes or other scrolling elements) by applying 'touch-action: manipulation' to the html element. See http://jsbin.com/tipure/ and http://jsbin.com/jucuna. This is issue w3c#19. This change also moves the core processing model details up to above the specific value definitions to make it easier to follow without getting lost in all the value-specific notes.
|
@jacobrossi I agonized over this text to try to be precise while also avoiding specific gesture details. After an hour, this was the best I could come up with. Do you think it's an improvement? I'd like to add a web-platform-test case for this, but since which elements support "non-continuous zooming" is out of scope of the spec, I guess I can't - right? Hopefully the jsbin demos are good enough. Now to fix blink.... |
|
In particular, here's the relevant text (since I also foolishly shifted some things around in the same CL):
|
|
I talked with @jacobrossi offline and he agreed that (while not perfect) this was definitely a step in the right direction and we should just land it and continue to iterate. |
Fix the touch-action processing model for zoom scenarios
It's incorrect to consider the touch-action values only up to the nearest
ancestor that supports ANY default touch behavior. Eg. in Edge you can
disable double-tap to zoom across an entire page (including any iframes
or other scrolling elements) by applying 'touch-action: manipulation' to
the html element. See http://jsbin.com/tipure/ and http://jsbin.com/jucuna.
This is issue #19.
This change also moves the core processing model details up to
above the specific value definitions to make it easier to follow
without getting lost in all the value-specific notes.