- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jun 2016 20:33:41 +0000
- To: public-pointer-events@w3.org
NavidZ has just created a new issue for https://github.com/w3c/pointerevents: == Click event while a pointer event is captured == Consider this scenario in the [following page](https://output.jsbin.com/zuwiwep): 1. Mousedown on blue. Mouseup on blue. 2. Mousedown on green. Mouseup o green. 3. Mousedown on blue. Move to green. Mouseup on green. 3. Mousedown on green. Move to blue. Mouseup on blue. Here is the output of Edge (and it is the same in current Chrome canary with pointer event flags on): // ==== 1 blue pointerdown Set pointer capture to blue div blue gotpointercapture blue pointerup blue click blue lostpointercapture // ==== 2 green pointerdown Set pointer capture to blue div blue gotpointercapture blue pointerup green click blue lostpointercapture // ==== 3 green pointerdown Set pointer capture to blue div blue gotpointercapture blue pointerup grey click blue lostpointercapture // ==== 4 blue pointerdown Set pointer capture to blue div blue gotpointercapture blue pointerup grey click blue lostpointercapture The question here is about the click event. In scenarios 2, 3, and 4 they all go to an element that doesn't have capture. Is that expected? Do we like to also direct click/contextmenu event to the captured element or suppress it altogether if it is not targeted at the capturing element? Or do we want to maybe call out that click or context menu events are not considered pointer events so they don't need to be redirected like capturing? I have a feeling that sending the click event as above is incorrect with the capturing scenarios as it is creating an inconsistent flow of events. I think maybe suppressing is the most reasonable action. what do you guys think? Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/75 using your GitHub account
Received on Wednesday, 1 June 2016 20:33:44 UTC