- From: Liviu Tinta via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Mar 2021 15:06:11 +0000
- To: public-pointer-events@w3.org
liviutinta has just created a new issue for https://github.com/w3c/pointerevents: == Order of pointer events across frames when using pointer capture == Regarding https://wpt.fyi/results/pointerevents/pointerevent_pointercapture_in_frame.html%3Fpen?label=experimental&label=master&aligned, in test 4 (Test penpointer capture in same-origin frame: Pointerdown with set capture at outer frame, then release on next pointermove). There are two frames, outerframe and innerframe. The inner frame is a same-origin frame. At pointerdown we call setPointerCapture on the outerframe, and at first pointermove event we call releasePointerCapture on outerframe, and pointerup in the innerframe. The usual order of events is (we only track pointerdown/gotpointercapture/lostpointercapture/pointerup and the first pointermove after pointerdown): - outerframe pointerdown - outerframe gotpointercapture - outerframe pointermove - outerframe lostpointercapture - innerframe pointerup However, when running the test against Chrome, I sometimes see the following order, and the test fails because of it: - outerframe pointerdown - outerframe gotpointercapture - outerframe pointermove - innerframe pointerup - outerframe lostpointercapture From reading the Pointer Events spec, I wasn't able to understand if there is a certain ordering of pointer events from the same sequence across frames. Is it fair to say that pointer events from the same sequence should be ordered per frame and not across frames? Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/355 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 March 2021 15:06:13 UTC