- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 30 Jul 2025 16:44:45 +0100
- To: public-pointer-events@w3.org
Dear all, the minutes from today's meeting are available on https://www.w3.org/2025/07/30-pointerevents-minutes.html and copied below. PEWG 30 July 2025 Agenda: https://www.w3.org/events/meetings/66591f6b-6694-4f90-b23d-bf8f1b9dda8a/20250730T110000/ IRC log: https://www.w3.org/2025/07/30-pointerevents-irc Attendees Present flackr, gastonr, mustaq, Patrick_H_Lauke Regrets smaug Chair: Patrick H. Lauke Scribe: Patrick H. Lauke * Web Platform Tests https://wpt.live/pointerevents/ / https://wpt.fyi/results/pointerevents?label=experimental&label=master&aligned * Recharter https://www.w3.org/2023/11/wg-pointer-events-charter.html * Any particular old or new issues that we want to start thinking about/tackling? https://github.com/w3c/pointerevents/issues # Web Platform Tests https://wpt.live/pointerevents/ / https://wpt.fyi/results/pointerevents?label=experimental&label=master&aligned Patrick: i know we now have all the tests, but wanted to get a feel for how we're actually doing with coverage in browsers mustaq: i see a big block of problems with the various -touch-action- related tests Patrick: I also see a lot of "harness ERROR" / "harness TIMEOUT" problems... mustaq: yes this may be down to webdriver not supporting touch. recently there's been some movement about testing touch in webdriver, but i don't know if this has been updated here <mustaq> What about proposing this part of Interop 2026? Patrick: so i think a good first step from here is to perhaps investigate the various harness problems. not sure if any of you have the ability/time to look at that? we may actually have less "red" than initially apparent Patrick: a lot of problems seem to be specifically in Safari+harness mustaq: another block is related to DOM changes Patrick: those are probably because these weren't defined properly anywhere, and we made a "sensible" call on this. not surprising that browsers haven't coalesced towards it Robert: yeah we were getting different results in all browsers. Is anybody at Apple aware/working on this? mustaq: i see that's part of interop so should be aware <mustaq> https://wpt.fyi/results/pointerevents?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2023-events <mustaq> Interop 2025 covers only ~2 of the DOM-change tests. Patrick: if only 2 in interop 2025, then worth making sure the remaining ones make it into interop 2026 mustaq: just checked, it's 3, not 2 Patrick: so i don't think it's a big worry the amount of red we have now, but would be good to at least investigate the cases where the harness is causing problems/not supporting the testing properly (particularly in Safari) Patrick: anybody want to officially take on the task of investigating what's going on with harness in WPT gastonr: i could give it a go mustaq: , but at last year's TPAC they mentioned they are working on their own webdriver (?) <mustaq> Safari mentioned adding WebDriver support for touch during last year TPAC but I don't know much beyond that. ACTION: Gaston to have look at WPT harness issues, Rob and Mustaq to help out/point in right direction if needed # Recharter https://www.w3.org/2023/11/wg-pointer-events-charter.html Patrick: i noticed that our charter runs out november 2025. I will get in touch with PLH to see what we need to do ACTION: Patrick to talk to PLH about charter extension/recharter # Any particular old or new issues that we want to start thinking about/tackling? https://github.com/w3c/pointerevents/issues Mustaq: we were looking at w3c/pointerevents#542 Patrick: pull request for this w3c/pointerevents#460 Rob: i'm aware of the problem about the pseudoelements Rob: ... we are looking at exposing events to pseudoelements (a separate attribute on the event) Rob: pretty sure this has been in CSS WG Rob: i think there is possible path. if we have that, then there's the possibility of solving issue with a pseudoelement target attribute. other alternatives, like a boundary for clicks that can be opted in Mustaq: do we expect those proposals to become part of PE? Rob: not necessarily...maybe CSS WG, but there's crossover similar to touch-action Mustaq: we need another issue then ... we need to hold back PR 460 Rob: the PR just says hold back sending click. and handwaves/magics away the exact HOW <mustaq> The list of options Rob suggested appears here: w3c/pointerevents#542 (comment) Patrick: I would say let's keep #460 for another 2 weeks until our next meeting, and then merge. just to make sure we're not missing a nuance Mustaq: i will be on vacation during our next meeting Patrick: we'll keep this short, unless there's any other open issues you want to discuss right now. thank you all for attending, see you next time # Summary of action items * Gaston to have look at WPT harness issues, Rob and Mustaq to help out/point in right direction if needed * Patrick to talk to PLH about charter extension/recharter -- 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, 30 July 2025 15:45:25 UTC