W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2014

[Bug 25215] New: Tweak to example 1 and what element touch-action is applied to

From: <bugzilla@jessica.w3.org>
Date: Mon, 31 Mar 2014 09:47:54 +0000
To: public-pointer-events@w3.org
Message-ID: <bug-25215-5978@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25215

            Bug ID: 25215
           Summary: Tweak to example 1 and what element touch-action is
                    applied to
           Product: PointerEventsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Pointer Events specification
          Assignee: jrossi@microsoft.com
          Reporter: redux@splintered.co.uk
        QA Contact: public-pointer-events-bugzilla@w3.org
                CC: public-pointer-events@w3.org

Currently, example 1 starts with

<style>
  /* Disable intrinsic user agent touch behaviors (such as panning or zooming)
so 
  that all events are given to the application instead. */

  html { 
    touch-action: none; 
  }
</style>

Personally, I find this a little heavy-handed and "dangerous". I've usually
advocated applying touch-action (and before that, in touch events,
preventDefault) more "surgically" just to the elements where it's needed, to
avoid developers cargo-culting overly broad snippets of css/js that kill all
browser defaults for everything.

I'd suggest applying it just to the canvas element in this example.

...
canvas {
  touch-action: none;
}
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 31 March 2014 09:48:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:26 UTC