Bug 21032 - Clarify goals of Pointer Events
Summary: Clarify goals of Pointer Events
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: Pointer Events Bugzilla list
Depends on:
Reported: 2013-02-18 01:48 UTC by Jacob Rossi [MSFT]
Modified: 2013-02-18 02:01 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Jacob Rossi [MSFT] 2013-02-18 01:48:21 UTC

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".
Comment 1 Jacob Rossi [MSFT] 2013-02-18 02:01:43 UTC
Change made per mailing list discussion: