- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Nov 2017 13:41:22 +0000
- To: public-pointer-events@w3.org
Sorry. I missed this one too before. Alright. You are right. We recently started sending pointercancel after drag operation starts and I intentionally for the first round didn't send the boundary events. We already hit some regressions in some js library by sending pointercancel when mouse starts dragging and we send pointercancel for it. But now we solved them and didn't hear anything else so far. Regarding the boundary events I believe we adhere to the spec and send the leave/out right after pointercancel. If Edge does that this is correct and as you said Chrome doesn't do that which is no spec compliant. btw, does Edge send pointercancel when dragstarts for the mouse? I didn't know they added that then. If so bravo to them :) Regarding the other question of when to start sending pointerevents again, spec never mentioned the same thing for scrolling case (which also caused pointercancel) either. So I'm not how to exactly include that in the spec to preferably cover all the cases. Do you have any suggestion? -- GitHub Notification of comment by NavidZ Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/222#issuecomment-341706178 using your GitHub account
Received on Friday, 3 November 2017 13:41:24 UTC