- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Feb 2016 21:50:39 +0000
- To: public-pointer-events@w3.org
This is a really interesting question, thanks @navidzolghadr! Basically I'd summarize this as: 1. We'd want pointer events to represent a consistent enter/leave sequence per pointer ID 2. For compatibility, mouse events should always present a self-consistent sequence 3. But multiple different pointer IDs all map to mouse events 4. And the spec implies there should be a 1:1 mapping from each pointer event to a compatibility mouse event We can't have all 4 properties. In the case above Edge seems to violate 1, but that seems like a real shame since it means developers using the new multi-point aware API don't get a self-consistent event stream. I'd personally rather violate 4 and maybe even 2 if necessary in edge cases. @teddink can you describe Edge's behavior here and what you consider by-design vs. a bug? Note that this is related to issue #7 which we still need to address in the spec somehow. -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/35#issuecomment-187929661 using your GitHub account
Received on Tuesday, 23 February 2016 21:50:41 UTC