- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 21 Dec 2022 16:28:58 +0000
- To: public-pointer-events@w3.org
Dear all, the minutes from today's meeting are at https://www.w3.org/2022/12/21-pointerevents-minutes.html and copied below: PEWG 21 December 2022 Agenda: https://www.w3.org/events/meetings/0d3af70c-0054-43dc-9c15-c60c5b9c3f3c/20221221T110000 Attendees: Patrick_H_Lauke, smaug Chair: Patrick H. Lauke Scribe: Patrick H. Lauke * Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445 * Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356 Olli: I think Mustaq has done a lot of triaging for us Patrick: Yes, I've seen a flurry of activity on https://github.com/w3c/pointerevents/ Patrick: as an aside, smaug, here's the bookmarks I always have to reopen and refer to for this meeting to remember how to use W3C tools https://www.w3.org/2002/03/RRSAgent and https://www.w3.org/2008/04/scribe.html # Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445 https://github.com/w3c/pointerevents/issues?page=1&q=is%3Aclosed+label%3Awpt Patrick: Mustaq has done a lot of commenting on these Patrick: correct link https://github.com/w3c/pointerevents/labels/wpt Olli: the last one here https://github.com/w3c/pointerevents/issues/457 is a chrome bug, so hoping that Chrome folks will do a test. let me change it to needs-wpt Patrick: so all the PRs (which are closed, as they were done) that need WPTs are here https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+ Olli: the most worrying one is https://github.com/w3c/pointerevents/pull/318 - this has been in spec for 2 years, and nobody has implemented it afaik Olli: need to see if there's a reason for this ... is it because it can't be implemented? not needed anymore? Olli: perhaps we need some telemetry data to see how often they're used in non-secure contexts, because if the usage is high, that will be tricky ACTION: discuss https://github.com/w3c/pointerevents/pull/318 in the new year and see what the situation is/why it's not been implemented # Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356 Patrick: don't think there's been any activity. We probably should also discuss this in the new year, because this is the last hanging item Olli: it would be good to get Apple people's take on this Patrick: maybe we can prod them in the new year. but otherwise we need to make a decision here on how to proceed either way Patrick: perhaps see if we can reach out to Jen Simmons who is pushing the public face of Apple's web standards developer outreach, or perhaps Antoine Quint https://github.com/graouts ACTION: reach out to Apple in new year to get feedback on #356 <Github> https://github.com/w3c/pointerevents/issues/356 : Clarify what the target of the click event should be after capturing pointer events [some more general discussion about the state we're in with other issues marked for future, and how they'll be quite valuable to look at once PE3 is out - either for a PE4, or a PE living standard] Patrick: if there's nothing else, I'd say have a relaxing break, and we'll reconvene in the new year for the next meeting -- Patrick H. Lauke https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Wednesday, 21 December 2022 16:29:13 UTC