- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Apr 2016 15:35:46 +0000
- To: public-pointer-events@w3.org
In practice I suspect either option will be fine for web compat. There are already other ways the mouse event sequence can be violated (eg. window covered temporarily or window moved, many browsers don't properly report mouse state transitions). I agree that solution B is cleaner, but it's more different from what Edge has already shipped. If Edge folks have a reason to prefer solution A that's OK with me. I agree that in any multi-modality scenario mouse events are always going to be a hack, so anything that is shown to be largely compatible with the existing web is fine (and arguably even preferable to changing behavior in a way that could change site behavior in a new way). @teddink Can you please link to a public bug tracking this issue in Edge? -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/35#issuecomment-214398644 using your GitHub account
Received on Monday, 25 April 2016 15:35:48 UTC