- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Jun 2017 19:12:55 +0000
- To: public-pointer-events@w3.org
@dtapuska mentioned a scenario that I missed earlier. @smaug---- @appsforartists, the long press touch causes the drag to start and since we have an implicit capturing for touches then if we were to give priority to capture over drag then the drag can never possibly start with touch on the web pages that don't know about pointer events and don't explicitly release the capture on touches! I don't think this is acceptable as it is a breaking change for dragging of touches. As opposed to what I said [earlier](https://github.com/w3c/pointerevents/issues/205#issuecomment-301817268): > We can go either way. The initial discussion ... we can not go either way. So basically capture cannot take priority over capture because I the reason I mentioned. Circling back to [my first solution](https://github.com/w3c/pointerevents/issues/205#issuecomment-301801904): - `pointercancel` (and `lostpointercapture` if needed) will be dispatched immediately before `dragstart`. - If the author doesn't like that, the author ought to `downEvent.preventDefault()` to prevent drag from occurring. I believe we agreed on this solution as well before this "capture priority over DnD" came into the picture. So are we still good with this solution here? -- GitHub Notification of comment by NavidZ Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/205#issuecomment-310474995 using your GitHub account
Received on Thursday, 22 June 2017 19:13:01 UTC