- From: Brenton Simpson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 May 2017 18:36:48 +0000
- To: public-pointer-events@w3.org
@mustaqahmed I'm not sure I'm following your points. It sounds like you disagree with my objections about using `downEvent.preventDefault()` to prevent `dragstart` from triggering `pointercancel`, but I'm not sure you understand my concerns. It sounds to me like the @NavidZ's recommendation so far is: - `pointercancel` will be dispatched immediately before `dragstart`. - If the author doesn't like that, the author ought to `downEvent.preventDefault()` to prevent drag from occurring. My objection is that this isn't granular enough. _Most_ default browser actions (like panning and clicking) should still be permitted. Therefore, I think `pointercancel` ought to only be dispatched if `dragStart.preventDefault()` hasn't been called, which means it should come after `dragstart`. Does that make sense? Are we all on the same page? -- GitHub Notification of comment by appsforartists Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/205#issuecomment-301564961 using your GitHub account
Received on Monday, 15 May 2017 18:36:54 UTC