- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Dec 2024 21:46:13 +0000
- To: public-pointer-events@w3.org
mustaqahmed has just created a new issue for https://github.com/w3c/pointerevents: == Implicit pointer capture state after a failed explicit capture call at `pointerdown` == The implicit capture is like calling `setPointerCapture()` right before the invocation of `pointerdown` listeners, see [Sec9.4](https://w3c.github.io/pointerevents/#implicit-pointer-capture). As a result, if an explicit `setPointerCapture()` call at `pointerdown` fails for any reason mentioned in [Sec9.2](https://w3c.github.io/pointerevents/#setting-pointer-capture), the implicit capture remains effective. This is a subtle point that we (browser engineers) missed when writing [this WPT](https://wpt.fyi/results/pointerevents/pointerevent_pointercapture_in_frame.html%3Ftouch?label=experimental&label=master&aligned), and it caused the WPT to fail with touch `pointerType`: the WPT expects certain explicit calls to fail but the implicit calls remain effective. I think the spec should clarify this point for developers who are not expected to follow the Sec9.2 algorithms. Thoughts? Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/534 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 December 2024 21:46:14 UTC