- From: Masayuki Nakano via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 May 2025 05:22:45 +0000
- To: public-pointer-events@w3.org
masayuki-nakano has just created a new issue for https://github.com/w3c/pointerevents: == Clarify what happens if capturing element is changed in a `lostpointercapture` listener == While an element captures a pointer, the pointer capture API call may cause `lostpointercapture` at next pointer event dispatching. Then, a `lostpointercapture` event listener can change the pending capture element with either `setPointerCapture` and `releasePointerCapture`. If so, I think if `releasePointerCapture` clears the pending one, following `gotpointercapture` should not be fired. Additionally, if `setPointerCapture` changes the pending one, `gotpointercapture` should be fired on the new pending element immediately instead of the old pending element and at the next processing of pending pointer capture. However, I don't find the definition about this situations. Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/550 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 May 2025 05:22:46 UTC