15:00:34 RRSAgent has joined #pointerevents 15:00:38 logging to https://www.w3.org/2025/03/26-pointerevents-irc 15:02:22 flackr has joined #pointerevents 15:02:38 Meeting: PEWG 15:02:50 Chair: Patrick H. Lauke 15:02:54 Scribe: Patrick H. Lauke 15:03:00 ScribeNick: Patrick_H_Lauke 15:03:22 Agenda: https://www.w3.org/events/meetings/66591f6b-6694-4f90-b23d-bf8f1b9dda8a/20250326T110000/ 15:03:55 TOPIC: Call for consensus 15:04:57 Patrick: call for consensus went out last week, gave it until yesterday. Not heard any negatives, so the call for consensus is officially passed 15:05:31 Patrick: CfC was here https://lists.w3.org/Archives/Public/public-pointer-events/2025JanMar/0059.html 15:05:46 TOPIC: Pointer Events Level 3 - next steps https://lists.w3.org/Archives/Public/public-pointer-events/2025JanMar/0061.html 15:06:30 Patrick: one thing PLH has already done is to update the intro to the spec, to highlight changes from PE2 15:09:37 Patrick: on the question "How long should the CR minimal duration be? 28 days or longer?" i will check with Philippe about what the best approach would be ... 15:09:50 (no worries philippe) 15:10:06 Patrick: "On Implementation report, looking at lack of implementations" 15:11:04 Patrick: need to refresh my mind based on what we did with PE2 - don't recall it being too onerous though 15:11:39 Patrick: Philippe also noted some discrepancies with tests, so need to double-check those 15:11:46 https://wpt.fyi/results/pointerevents?label=experimental&label=master&aligned 15:12:55 TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445 / https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+ 15:19:46 present+ 15:19:51 present+ flackr 15:19:57 present+ adettenb 15:20:31 Patrick: we have 3 outstanding "needs-WPT" for v3. worth looking at these soon, as we'll need these for implementation report 15:20:36 TOPIC: AOB 15:21:13 Adam: was looking at one of the unit tests relating to chorded buttons, and it was unclear what actual behaviour should be after reading through the spec 15:21:40 https://www.w3.org/TR/uievents/#dom-mouseevent-buttons 15:21:41 [Adam provides more details about scenarios where it's unclear] 15:22:19 Rob: if you ignore presciptive part of the spec, it seems that "buttons" is just a bitmask 15:22:43 Adam: buttons is a bitmask, but button isn't 15:23:24 Rob: button is the one that just relates to the change of state - e.g. auxclick is triggered by button 3, which is bitmask 4 ... 15:23:47 Rob: and buttons could then have any other buttons you're pressing/holding 15:26:34 [more discussion on some examples, e.g. "if i press left mouse button and keep it down, and then press and release right mouse button, it would fire auxclick, button would be right mouse button, but buttons would include both right and left mouse buttons"] 15:28:50 Patrick: reminder that if there's questions, particularly very specific ones that go into detailed scenarios, feel free to open an issue in GH for us to look at/discuss async 15:29:01 Patrick: thank you all, catch you again in 2 weeks' time 15:29:11 RRSAgent, make logs world-visible 15:29:15 RRSAgent, generate minutes 15:29:16 I have made the request to generate https://www.w3.org/2025/03/26-pointerevents-minutes.html Patrick_H_Lauke 15:29:42 rrsagent, bye 15:29:42 I see no action items