21032 2013-02-18 01:48:21 +0000 Clarify goals of Pointer Events 2013-02-18 02:01:43 +0000 1 1 1 Unclassified PointerEventsWG Pointer Events specification unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 jrossi jrossi public-pointer-events public-pointer-events-bugzilla oldest_to_newest 83247 0 jrossi 2013-02-18 01:48:21 +0000 http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0127.html 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". 83248 1 jrossi 2013-02-18 02:01:43 +0000 Change made per mailing list discussion: http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0130.html Change: https://dvcs.w3.org/hg/pointerevents/rev/c1b43b6dec23