- From: Matt Brubeck via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Oct 2015 17:46:45 +0000
- To: public-pointer-events@w3.org
I'm hesitant to say that these two values are "equivalent" since `touch-action: auto` may (and in practice does) allow more default actions than `touch-action: pan-x pan-y`. Even with the "with regards to scroll handling" qualifier, it seems like this might confuse things more than clarify them. However, maybe we can expand the definition of `auto` to explicitly say that it allows panning in both directions, as well as zooming and possibly other actions? The author of the hammer.js code seems to have reversed the meanings of *all* `touch-action` values. The confusion doesn't seem specifically related to `auto` or `pan-x pan-y`. For example, a simple `touch-action: pan-x` was reversed in meaning. I don't think adding text specifically about `auto` being equivalent to `pan-x pan-y` would help prevent that. Perhaps instead we should add some more code samples, and clarify the existing ones. -- GitHub Notif of comment by mbrubeck See https://github.com/w3c/pointerevents/issues/23#issuecomment-146274995
Received on Wednesday, 7 October 2015 17:46:47 UTC