13:58:38 <RRSAgent> RRSAgent has joined #pointerevents
13:58:42 <RRSAgent> logging to https://www.w3.org/2026/06/03-pointerevents-irc
13:58:44 <Patrick_H_Lauke> Meeting: PEWG
13:58:48 <Patrick_H_Lauke> Chair: Patrick H. Lauke
13:58:52 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
13:58:59 <Patrick_H_Lauke> ScribeNick: Patrick_H_Lauke
13:59:23 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/bc0bed33-fd93-40a6-95bb-10f27c641863/20260603T100000/
13:59:34 <Patrick_H_Lauke> present+
14:03:14 <Patrick_H_Lauke> present+ smaug
14:04:01 <smaug> https://webengineshackfest.org/
14:05:47 <flackr> flackr has joined #pointerevents
14:05:59 <Patrick_H_Lauke> present+ flackr
14:08:27 <mustaq> mustaq has joined #pointerevents
14:08:42 <Patrick_H_Lauke> present+ vmpstr
14:08:47 <Patrick_H_Lauke> present+ mustaq
14:08:51 <Patrick_H_Lauke> present+ plh
14:09:10 <Patrick_H_Lauke> TOPIC: Status of WG charter
14:10:02 <Patrick_H_Lauke> plh: has been sent for review, deadline end of June. should be smooth, people will remain in the WG, purely administrative at the moment
14:10:36 <Patrick_H_Lauke> plh: as soon as we incubated an explainer for gestures, we can recharter - we won't have to wait for 2 years though
14:10:56 <Patrick_H_Lauke> plh: we can make room in this WG to incubate
14:11:16 <Patrick_H_Lauke> TOPIC: PE Level 3 status
14:11:48 <Patrick_H_Lauke> plh: also under AC review, sent it after extending group charter. once we have new charter, we can forget about PE 3. i will then remove PE 2
14:12:42 <Patrick_H_Lauke> plh: and next time we'll be more strict about PE 4 shipping ... unlike PE 3 that got stuck for a long time trying to finalise one last feature
14:12:54 <Patrick_H_Lauke> plh: thank you all for your work on the tests/test results
14:13:14 <Patrick_H_Lauke> TOPIC: Broken links in Pointer Events #641 https://github.com/w3c/pointerevents/issues/641
14:14:00 <mustaq> mustaq has joined #pointerevents
14:14:08 <Patrick_H_Lauke> plh: this got fixed by itself when we republished PE3. can be closed
14:14:11 <Patrick_H_Lauke> patrick: done
14:14:40 <Patrick_H_Lauke> TOPIC: action from last meeting Patrick to file an issue on PE about removing reliance on/reference to remaining UI events, we can flesh out further
14:15:26 <Patrick_H_Lauke> patrick: gave myself a task to file an issue. not looked in depth but specific issue is here https://github.com/w3c/pointerevents/issues/644
14:16:31 <Patrick_H_Lauke> patrick: wondering if we can firm things up a bit ... like the move of keyboard event potentially to editing WG
14:17:05 <mustaq> mustaq has joined #pointerevents
14:17:07 <Patrick_H_Lauke> plh: timing is unfortunate for us to do it, as it's not in charter
14:18:43 <Patrick_H_Lauke> ACTION: plh to look into talking to editing WG to take over keyboard part of UI events
14:19:50 <Patrick_H_Lauke> plh: fundamentally not a PE issue though
14:20:31 <Patrick_H_Lauke> patrick: yes, it's just that we stripped UI events for parts for what we need, so the remaining bit is keyboard so this is more a courtesy for editing WG to deal with taking over the orphaned remains
14:21:08 <Patrick_H_Lauke> TOPIC: action from last time mustaq to look at moving/removing references to UI events related to pointerlock spec
14:21:45 <Patrick_H_Lauke> mustaq: didn't have time, can look at it soon
14:21:50 <Patrick_H_Lauke> plh: if you need help, let me know
14:21:59 <Patrick_H_Lauke> plh: i can make PR for pointerlock
14:23:03 <Patrick_H_Lauke> ACTION: plh to move pointerlock-related parts of UI events to pointerlock
14:23:30 <Patrick_H_Lauke> TOPIC: Any "MouseEvent" issues that need to be prioritised? https://github.com/w3c/pointerevents/issues?q=is%3Aissue%20state%3Aopen%20label%3AMouseEvent
14:25:04 <Patrick_H_Lauke> patrick: happy to do it async, or we do it now
14:25:57 <Patrick_H_Lauke> plh: editorial: we need to harmonise in our spec how we present events. currently there's a mix of styles
14:26:16 <Patrick_H_Lauke> patrick: i'll look at this, report back next time
14:26:49 <Patrick_H_Lauke> ACTION: Patrick to look at harmonising how events are presented (old UI events style and our own legacy way)
14:27:12 <Patrick_H_Lauke> plh: should prioritise mouse events and pointer events in terms of initialisation
14:27:54 <Patrick_H_Lauke> flackr: one thing we were missing originally was an authoritative target. ui events was handwavy there, and we had trouble piggy-backing on that. now that we took ownership, we control the dispatch algo
14:28:23 <Patrick_H_Lauke> ACTION: flackr to look at any duplication we now have about event dispatch/initialisation
14:28:54 <Patrick_H_Lauke> mustaq: the handwavy prose about out and in events and how they're fired
14:29:46 <mustaq> Old handwavy mouse boundary event "spec": https://w3c.github.io/pointerevents/#mouse-event-order
14:29:56 <Patrick_H_Lauke> plh: dispatch first, then initialisation. once clarified those, then we can move event by event to make sure they're consistent. and then hit testing, because it's super easy /s
14:31:03 <flackr> https://drafts.csswg.org/css-ui/#pointer-events-control
14:33:21 <Patrick_H_Lauke> plh: do we need to look at event order?
14:34:07 <Patrick_H_Lauke> flackr: the mouse-related order is still valid, but then the question about when exactly they interleave
14:34:23 <Patrick_H_Lauke> patrick: because originally in PE we were quite handwavy about the order you MIGHT get
14:35:09 <Patrick_H_Lauke> flackr: now the dispatch should also care about pointer capture, which will be nice
14:35:56 <Patrick_H_Lauke> TOPIC: TPAC
14:36:03 <Patrick_H_Lauke> patrick: when's the deadline for TPAC?
14:37:34 <Patrick_H_Lauke> plh: deadline 17 June. who's going?
14:37:42 <Patrick_H_Lauke> Patrick: I am
14:37:45 <Patrick_H_Lauke> Olli: I am
14:38:19 <Patrick_H_Lauke> (others unlikely)
14:41:20 <Patrick_H_Lauke> plh: we don't necessarily need our own meeting slot. can always ask other chairs if they want somebody from PE and we can go into their meetings
14:41:54 <Patrick_H_Lauke> Group decided not to have a specific meeting slot, but for those there happy to join other groups on request
14:42:51 <Patrick_H_Lauke> Olli: so should we go async through the existing issues in https://github.com/w3c/pointerevents/issues?q=is%3Aissue%20state%3Aopen%20label%3AMouseEvent about dispatch?
14:43:01 <Patrick_H_Lauke> plh: yes, and then move to initialisation
14:43:37 <smaug> Tiny bit related to dispatch. https://mozilla.pettay.fi/composed-events-dispatch.html is a visualization for .relatedTarget and .composed
14:44:38 <Patrick_H_Lauke> rrsagent, make logs world-visible
14:44:45 <Patrick_H_Lauke> rrsagent, generate minutes
14:44:46 <RRSAgent> I have made the request to generate https://www.w3.org/2026/06/03-pointerevents-minutes.html Patrick_H_Lauke
14:48:04 <Patrick_H_Lauke> rrsagent, bye
14:48:04 <RRSAgent> I see 4 open action items saved in https://www.w3.org/2026/06/03-pointerevents-actions.rdf :
14:48:04 <RRSAgent> ACTION: plh to look into talking to editing WG to take over keyboard part of UI events [1]
14:48:04 <RRSAgent>   recorded in https://www.w3.org/2026/06/03-pointerevents-irc#T14-18-43
14:48:04 <RRSAgent> ACTION: plh to move pointerlock-related parts of UI events to pointerlock [2]
14:48:04 <RRSAgent>   recorded in https://www.w3.org/2026/06/03-pointerevents-irc#T14-23-03
14:48:04 <RRSAgent> ACTION: Patrick to look at harmonising how events are presented (old UI events style and our own legacy way) [3]
14:48:04 <RRSAgent>   recorded in https://www.w3.org/2026/06/03-pointerevents-irc#T14-26-49
14:48:04 <RRSAgent> ACTION: flackr to look at any duplication we now have about event dispatch/initialisation [4]
14:48:04 <RRSAgent>   recorded in https://www.w3.org/2026/06/03-pointerevents-irc#T14-28-23