14:02:01 <RRSAgent> RRSAgent has joined #pointerevents
14:02:05 <RRSAgent> logging to https://www.w3.org/2026/06/17-pointerevents-irc
14:02:06 <Patrick_H_Lauke> Meeting: PEWG
14:02:10 <Patrick_H_Lauke> Chair: Patrick H. Lauke
14:02:17 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
14:02:39 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/bc0bed33-fd93-40a6-95bb-10f27c641863/20260617T100000/
14:02:42 <Patrick_H_Lauke> present+
14:02:45 <Patrick_H_Lauke> present+ plh
14:02:49 <Patrick_H_Lauke> present+ mustaq
14:02:56 <Patrick_H_Lauke> present+ flackr
14:03:07 <Patrick_H_Lauke> regrets+ smaug
14:04:41 <Patrick_H_Lauke> TOPIC: harmonising how events are presented (old UI events style and our own legacy way)
14:05:48 <Patrick_H_Lauke> plh: reminder that next week will be the deadline for AC review of charter and PE3 to REC. poke your rep if they haven't voted already
14:13:31 <Patrick_H_Lauke> Patrick: i've been looking at how pointerevents has been listing/explaining the interfaces and events. we use dictionary and event interface with the IDL, and for each individual event (like pointerdown) we then just use prose. in mouse events and wheel events it splits the interface and the init dictionary, and for each event it provides a whole table. which one do we prefer/want?
14:14:17 <mustaq> mustaq has joined #pointerevents
14:14:58 <Patrick_H_Lauke> mustaq: for all the mouse events, there seems to be a LOT of info there that is always the same...quite redundant
14:15:30 <Patrick_H_Lauke> flackr: we could probably look at removing redundant context stuff, and make sure that everything is captured appropriately in the definition
14:19:13 <Patrick_H_Lauke> [we looked specifically at information such as "where do i find out if a pointer event bubbles" ... instead of listing this it specifically for each event like mouse does, it has https://w3c.github.io/pointerevents/#attributes-and-default-actions]
14:29:18 <Patrick_H_Lauke> ACTION: Patrick to merge the event and init definitions for mouse and wheel into a single one, like we do for pointervents, and remove context row from all the mouse/wheel specific event tables (and remove any other redundant info), making sure to hoist any relevant info back to the definitions at the start
14:30:27 <mustaq> FYI: UIEvent.detail is used only in click-like event and mousedown/up:
14:30:27 <mustaq> https://developer.mozilla.org/en-US/docs/Web/API/UIEvent/detail
14:31:55 <Patrick_H_Lauke> ACTION: Patrick to consider tweaking introduction/abstract to explain why all of a sudden there are mouse and wheel events in there too
14:33:12 <Patrick_H_Lauke> TOPIC: plh to look into talking to editing WG to take over keyboard part of UI events
14:33:36 <Patrick_H_Lauke> plh: reached out, timeline around TPAC
14:33:52 <Patrick_H_Lauke> TOPIC: plh to move pointerlock-related parts of UI events to pointerlock
14:34:06 <Patrick_H_Lauke> plh: not contacted yet, still on my todo list
14:35:02 <Patrick_H_Lauke> mustaq: i looked at this, pointerlock spec already includes everything we need, so my suggestion would be to remove the algo in UI events spec, and change references to point directly to pointerlock
14:35:48 <Patrick_H_Lauke> plh: will this affect WPTs ? don't think it would... but double-check if any pointerlock tests as part of ui events set of tests
14:36:37 <Patrick_H_Lauke> plh: also check MDN/browser data... my guess is you won't need to do that for pointerlock
14:37:05 <Patrick_H_Lauke> TOPIC: flackr to look at any duplication we now have about event dispatch/initialisation
14:38:07 <Patrick_H_Lauke> Patrick: we've probably covered the initialisation. for dispatch, let's tackle it after that's resolved, as that will be trickier
14:38:58 <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:39:51 <Patrick_H_Lauke> plh: last time we said we want to look at dispatch first, so after we've done the first cleanup of the structure for initialisation first, we should look at the dispatch-specific ones
14:40:03 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/issues?q=is%3Aissue%20state%3Aopen%20label%3AMouseEvent%20dispatch
14:46:53 <Patrick_H_Lauke> rrsagent, set logs world-visible
14:47:03 <Patrick_H_Lauke> rrsagent, generate minutes
14:47:04 <RRSAgent> I have made the request to generate https://www.w3.org/2026/06/17-pointerevents-minutes.html Patrick_H_Lauke
14:48:04 <Patrick_H_Lauke> rrsagent, bye
14:48:04 <RRSAgent> I see 2 open action items saved in https://www.w3.org/2026/06/17-pointerevents-actions.rdf :
14:48:04 <RRSAgent> ACTION: Patrick to merge the event and init definitions for mouse and wheel into a single one, like we do for pointervents, and remove context row from all the mouse/wheel specific event tables (and remove any other redundant info), making sure to hoist any relevant info back to the definitions at the start [1]
14:48:04 <RRSAgent>   recorded in https://www.w3.org/2026/06/17-pointerevents-irc#T14-29-18
14:48:04 <RRSAgent> ACTION: Patrick to consider tweaking introduction/abstract to explain why all of a sudden there are mouse and wheel events in there too [2]
14:48:04 <RRSAgent>   recorded in https://www.w3.org/2026/06/17-pointerevents-irc#T14-31-55