[Bug 21032] New: Clarify goals of Pointer Events


            Bug ID: 21032
           Summary: Clarify goals of Pointer Events
    Classification: Unclassified
           Product: PointerEventsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Pointer Events specification
          Assignee: jrossi@microsoft.com
          Reporter: jrossi@microsoft.com
        QA Contact: public-pointer-events-bugzilla@w3.org
                CC: public-pointer-events@w3.org


Rick Byers:
I'm concerned that these may help perpetuate the misconception that if you
design for pointers, you don't need to think explicitly about how to design
your UI for different input types.  There are still lots of challenges to
designing a UI that works well with both touch and mouse, for example,
appropriate target size, gesture support (you'd never 'swipe' with the mouse),
etc.  I propose we change "easy" to "easier", and replace the second sentence
with something like:

> So authors can easily code to Pointer Events to share logic between different input types where it makes sense, and customize for a particular type of input only where necessary to get the best experience.

Also, if we're tweaking the introduction, I'd suggest we also add a sentence or
two around the threaded scrolling implications (to me that's an even more
important property than unifying different input types).  Perhaps after the
"primary goal" sentence we can say something like "An additional key goal is to
enable multi-threaded user agents to handle default touch actions such as
scrolling without blocking on JavaScript".

You are receiving this mail because:
You are on the CC list for the bug.

Received on Monday, 18 February 2013 01:48:23 UTC