16:01:08 RRSAgent has joined #pointerevents 16:01:12 logging to https://www.w3.org/2022/12/21-pointerevents-irc 16:02:31 present+ Patrick_H_Lauke 16:02:40 present+ smaug 16:02:46 Meeting: PEWG 16:02:56 Chair: Patrick H. Lauke 16:03:05 Scribe: Patrick H. Lauke 16:03:11 ScribeNick: Patrick_H_Lauke 16:03:19 Agenda: https://www.w3.org/events/meetings/0d3af70c-0054-43dc-9c15-c60c5b9c3f3c/20221221T110000 16:03:35 Olli: I think Mustaq has done a lot of triaging for us 16:03:52 Patrick: Yes, I've seen a flurry of activity on https://github.com/w3c/pointerevents/ 16:04:41 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 16:08:33 TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445 16:08:33 https://github.com/w3c/pointerevents/issues?page=1&q=is%3Aclosed+label%3Awpt 16:08:44 Patrick: Mustaq has done a lot of commenting on these 16:09:14 Patrick: correct link https://github.com/w3c/pointerevents/labels/wpt 16:09:47 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 16:10:42 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+ 16:11:14 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 16:11:37 Olli: need to see if there's a reason for this ... is it because it can't be implemented? not needed anymore? 16:12:32 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 16:12:57 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 16:14:22 TOPIC: Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356 16:14:42 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 16:15:25 Olli: it would be good to get Apple people's take on this 16:15:50 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 16:17:46 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 16:17:56 ACTION: reach out to Apple in new year to get feedback on #356 16:17:56 https://github.com/w3c/pointerevents/issues/356 : Clarify what the target of the click event should be after capturing pointer events 16:24:10 [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] 16:24:30 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 16:24:37 RRSAgent, set logs world-visible 16:24:45 RRSAgent, generate minutes 16:24:46 I have made the request to generate https://www.w3.org/2022/12/21-pointerevents-minutes.html Patrick_H_Lauke 16:25:07 rrsagent, set logs world-visible 16:25:15 rrsagent, bye 16:25:15 I see 2 open action items saved in https://www.w3.org/2022/12/21-pointerevents-actions.rdf : 16:25:15 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 [1] 16:25:15 recorded in https://www.w3.org/2022/12/21-pointerevents-irc#T16-12-57 16:25:15 ACTION: reach out to Apple in new year to get feedback on #356 [2] 16:25:15 recorded in https://www.w3.org/2022/12/21-pointerevents-irc#T16-17-56 16:25:22 https://github.com/w3c/pointerevents/issues/356 : Clarify what the target of the click event should be after capturing pointer events