- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Apr 2016 20:08:15 +0000
- To: public-pointer-events@w3.org
Thanks! Notes from discussion on the call today [are here](https://www.w3.org/2016/04/26-pointerevents-minutes.html#item05). Our main concern is the potential for broken-looking UX when switching between mouse and touch input devices on a website designed only for mouse events (not at all an uncommon scenario). Eg. move the mouse over one hover menu then tap on another as in [this example](http://output.jsbin.com/tubiro?quiet=1). With current Chrome and Edge behavior you shouldn't get into a state where both menus are open at once, but with [Ted's proposal](#issuecomment-192506739) you would. Also it seems wrong for the pointer events spec to define a sequence of mouse events which is inconsistent with the UI Events spec. Perhaps we could simplify this by having the PE spec define the behavior of a virtual "legacy" mouse device, and leaving the specific generation of mouseover/enter/leave/out events up to the definition in UI Events? @mustaqahmed is going to propose something along these lines. -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/35#issuecomment-214870557 using your GitHub account
Received on Tuesday, 26 April 2016 20:08:17 UTC