- From: Domenic Denicola via GitHub <sysbot+gh@w3.org>
- Date: Fri, 30 Jul 2021 22:28:40 +0000
- To: public-pointer-events@w3.org
I've merged the HTML spec patch, but it would be great if the follow-up PE tasks were properly defined before this issue was closed. My suggestion: define "fire a pointer cancelation" as something which fires the three events and properly initializes their pointerIds, and does the capture business. Then instead of saying "A user agent MUST fire a pointer event named pointercancel in the following circumstances:", say "The user agent must fire a pointer cancelation in the following circumstances:". And then update HTML to reference "fire a pointer cancelation" instead of the current vague language about follow-up events. -- GitHub Notification of comment by domenic Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/384#issuecomment-890219263 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 30 July 2021 22:28:42 UTC