- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 26 Mar 2025 15:53:44 +0000
- To: public-pointer-events@w3.org
Dear all, the minutes for today's quick call are at https://www.w3.org/2025/03/26-pointerevents-minutes.html and copied below: PEWG 26 March 2025 Agenda: https://www.w3.org/events/meetings/66591f6b-6694-4f90-b23d-bf8f1b9dda8a/20250326T110000/ IRC log: https://www.w3.org/2025/03/26-pointerevents-irc Attendees adettenb, flackr, Patrick_H_Lauke Chair: Patrick H. Lauke Scribe: Patrick H. Lauke * Call for consensus * Pointer Events Level 3 - next steps https://lists.w3.org/Archives/Public/public-pointer-events/2025JanMar/0061.html * Meta-issue: update WPT to cover Pointer Events Level 3 w3c/pointerevents#445 / https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+ * AOB # Call for consensus Patrick: call for consensus went out last week, gave it until yesterday. Not heard any negatives, so the call for consensus is officially passed Patrick: CfC was here https://lists.w3.org/Archives/Public/public-pointer-events/2025JanMar/0059.html # Pointer Events Level 3 - next steps https://lists.w3.org/Archives/Public/public-pointer-events/2025JanMar/0061.html Patrick: one thing PLH has already done is to update the intro to the spec, to highlight changes from PE2 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 ... (no worries philippe) Patrick: "On Implementation report, looking at lack of implementations" Patrick: need to refresh my mind based on what we did with PE2 - don't recall it being too onerous though Patrick: Philippe also noted some discrepancies with tests, so need to double-check those https://wpt.fyi/results/pointerevents?label=experimental&label=master&aligned # Meta-issue: update WPT to cover Pointer Events Level 3 w3c/pointerevents#445 / https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+ Patrick: we have 3 outstanding "needs-WPT" for v3. worth looking at these soon, as we'll need these for implementation report # AOB 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 <flackr> https://www.w3.org/TR/uievents/#dom-mouseevent-buttons [Adam provides more details about scenarios where it's unclear] Rob: if you ignore presciptive part of the spec, it seems that "buttons" is just a bitmask Adam: buttons is a bitmask, but button isn't 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 ... Rob: and buttons could then have any other buttons you're pressing/holding [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"] 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 Patrick: thank you all, catch you again in 2 weeks' time -- Patrick H. Lauke * https://www.splintered.co.uk/ * https://github.com/patrickhlauke * https://flickr.com/photos/redux/ * https://mastodon.social/@patrick_h_lauke
Received on Wednesday, 26 March 2025 15:53:52 UTC