Add touch-action: manipulation #24
Comments
|
At the moment the 300ms delay is removed from Chrome stable and I believe FF is looking at removing it as well as looking into supporting touch-action (this is all second hand information so could be wrong). I'm going to play around with touch-action a little more and bolster what it currently says in the docs. |
|
@gauntface given our long conversation yesterday where I was wrapping my head around some of this. I feel like by the time this is "officially launched" then we will need something like this. I really like the idea of blocking out an image so that the developer can let them pan and zoom an image independently of scrolling on the page and not have the browser arse about by thinking the user might want to scroll. The use-case led approach would be for that type of interaction... rather than document touch-action: manipulation on its own. |
|
@PaulKinlan I agree with use case driven content. I still need to play around with touch-action more. In WP it makes sense since you often need to add a touch-action to get anything working with pointer event, in Chrome it makes less sense to use - it seems to be a good way to explicitly define what you want touches to do. Thinking on this, the reason the 300ms delay is removed when a touch-action is applied, is that most touch-action rules will disable double-tap-zoom (i.e. touch-action: pan-y | pan-x | manipulation | none). |
|
The manipulation property isn't in the spec anymore. Can't find the discussion about it |
|
Manipulation is in the editors draft here: And is supported in Chrome and IE which are the current browsers supporting touch-action. |
|
Yes, i found out that i was reading the wrong document. Oops |
|
I've updated the content for the touch-action section and included the 300ms removal as well as better descriptions. Would love any comments and feedback. |
# This is the 1st commit message: Adding start of Workbox v3 alpha docs # This is the commit message #2: Adding v3 alpha # This is the commit message #3: Adding configuration guide # This is the commit message #4: Adding workbox-precaching and fixing nested parameters # This is the commit message #5: Setting up namespaced docs on WF # This is the commit message #6: Adding ref and module docs for precaching # This is the commit message #7: Adding ref and module docs for precaching # This is the commit message #8: Routing Docs and module guide # This is the commit message #9: Routing Docs and module guide # This is the commit message #10: Adding workbox-cache-expiration guide and reference docs # This is the commit message #11: Adding routing docs # This is the commit message #12: Changing menu name # This is the commit message #13: Adding ability to use custom project yaml # This is the commit message #14: Adding workbox pages # This is the commit message #15: Getting it to work on devsite staging # This is the commit message #16: Adding some headings instead of sections but need to stage # This is the commit message #17: Moving to heading # This is the commit message #18: Adding heading support for navigation # This is the commit message #19: Adding contributor list # This is the commit message #20: Adding more content for docs # This is the commit message #21: Adding in company logos # This is the commit message #22: Adding in company logos # This is the commit message #23: Adding logos # This is the commit message #24: Adding some fixes for left nav # This is the commit message #25: Renaming strategies # This is the commit message #26: Fixng ref doc bug and add missing module pages # This is the commit message #27: Adding Guides etc
https://developers.google.com/web/fundamentals/documentation/user-input/touch-input/touchevents/index
I would add touch-action: manipulation, which is specifically for removing the 300ms click delay.
The text was updated successfully, but these errors were encountered: