- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Sat, 21 Oct 2017 02:30:30 +0000
- To: public-pointer-events@w3.org
Chrome 62 has just rolled out to stable and there's a (google internal) report of at least one site being broken by the `pointercancel` that occurs during a drag. @NavidZ @appsforartists can you summarize why you believe `pointercancel` is better than just what Edge is doing with `lostpointercapture` and `pointerleave` in this scenario? It seems reasonable to me that DnD would behave like some other element/frame coming in on top and capturing the pointer away (i.e. basically the same event stream as if I drag outside the window - we don't send `pointercancel` in that case either). We've missed the boat for keeping this change from getting into Chrome 62, so we've got a couple weeks to see what other reports we get of breakage. If there's none then perhaps either approach is fine. But if there's more, and there's not really compelling reason why cancellation is better than leaving then perhaps we should reconsider this change? -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/205#issuecomment-338358000 using your GitHub account
Received on Saturday, 21 October 2017 02:30:31 UTC