- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 6 May 2026 16:19:13 +0100
- To: public-pointer-events@w3.org
Dear all, the minutes from today's meeting can be found at https://www.w3.org/2026/05/06-pointerevents-minutes.html and copied below: PEWG 06 May 2026 Agenda: https://www.w3.org/events/meetings/bc0bed33-fd93-40a6-95bb-10f27c641863/20260506T100000/ IRC log: https://www.w3.org/2026/05/06-pointerevents-irc Attendees mustaq, nicolo-ribaudo, Patrick_H_Lauke, plh, smaug Chair: Patrick H. Lauke Scribe: Patrick H. Lauke * Expose 'inertial scrolling state' in wheel events w3c/pointerevents#587 * question about status of PE3 * follow-up from breakout day session about gestures * UI events TF meeting Patrick: still need to catch up with PLH about status of PE3 and how to tweak our charter with regards to gestures Patrick: but I did file our answer to w3c/webai-roadmap#26 Mustaq: question maybe if an AI wants to generate TRUSTED events <smaug> https://www.w3.org/groups/wg/pointer-events/calendar/ Patrick: i guess at that point, the AI/agent may want to run its own headless browser and fake trusted events somehow... Olli: we need to see if the UI Events TF meeting should still be there or removed from calendar Patrick: there is no UI Events TF as such anymore, is there? Olli: think Mike Smith was the first person to set this up # Expose 'inertial scrolling state' in wheel events w3c/pointerevents#587 Mustaq: i have a local patch ready, will send it <mustaq> Work in progress, expecting to send out a PR in a day or two. Patrick: opening this up to the the group now, are there any other issues you've seen that are worth discussing? https://github.com/w3c/pointerevents/issues Mustaq: i think w3c/pointerevents#628 can be closed ... we have those in pointer events? <mustaq> May be close w3c/pointerevents#628 as WAI? Mustaq: spec probably needs cleanup to not duplicate button info Olli: makes sense to close yes Mustaq: looking at w3c/pointerevents#633 Olli: this is about old IE properties <mustaq> Blink issue: https://crbug.com/40509957 Mustaq: have been discussing if we want to standardise it or not Olli: is there some rounding happening? old ones integer, modern ones double # question about status of PE3 <plh> w3c/transitions#779 (comment) plh: version 3 currently stalled. had a comment on march 13 asking for clarification for why certain tests are failing plh: do we want to go through them right now? Patrick: can probably start looking now... <plh> https://w3c.github.io/pointereventswg/implementation-reports/wpt-pointerevents-2026-01-25.html#file-26 plh: can we explain why those tests are failing in chrome/firefox? is it a test harness limitation, and then if so why is it passing in safari? mustaq: my understanding is that pen is not well supported at low level in webdriver. in some platforms. mustaq: like a big text box ... if you drag with mouse, it does text selection. with touch, it scrolls. with pen, it's not clear/varies by platform... mustaq: so it could be a windows vs macOS with test harness issue mustaq: safari could be treating pen as mouse inthe webdriver <plh> https://w3c.github.io/pointereventswg/implementation-reports/wpt-pointerevents-2026-01-25.html#file-31 olli: is this the one we discussed recently, where chrome was doing one thing, firefox something else... plh: so is the spec correct, but it's bugs in browsers? <smaug> https://github.com/web-platform-tests/wpt/commit/a9f4351e61506bfec0a0c111f22d164cf213aa1c mustaq: the test was wrong at some point. we fixed it in november...so we believe the test is correct now plh: do we have bugs filed in chrome/firefox for this? <mustaq> https://crbug.com/404479707#comment7 <smaug> web-platform-tests/wpt#56614 <mustaq> This behavior is not "fully" specified? <plh> https://w3c.github.io/pointereventswg/implementation-reports/wpt-pointerevents-2026-01-25.html#file-36 mustaq: safari test driver don't support touch mustaq: safari web driver has limited touch support, but not complete <plh> https://w3c.github.io/pointereventswg/implementation-reports/wpt-pointerevents-2026-01-25.html#file-90 plh: probably same reason as previous one mustaq: i think we meant to remove all touch-action tests olli: touch-action none should be supported everwhere. why is it not passing in firefox? can't remember, will need to check plh: could be a corner case if we have a whole bunch of other tests passing in firefox olli: firefox harness doesn't support pen <mustaq> https://wpt.fyi/results/pointerevents/pointerevent_iframe-touch-action-none_touch.html?label=experimental&label=master&aligned plh: for the test where the behaviour is not fully specified, do we have an issue to track that? olli: for the remove from slot case? yeah there's an issue in WPT, but not sure where the issue should go. could even go to DOM spec. mustaq: what do we do for OUR test though? mark as tentative? olli: yeah, maybe best to file an issue in our repo mustaq: so i'll file an issue in our repo <mustaq> ...and mark the test as tentative on that issue. # follow-up from breakout day session about gestures Patrick: can't quite remember what we agreed regarding gestures and charter plh: i don't think we had fully decided, but my suggestion would be to remove mention of gestures from our current rechartering proposal, incubate regardless as part of our time, and once we have matured it more we can recharter with more concrete proposal Patrick: what do we need to do to make it official in WICG plh: i think they need two organisations to lend support <smaug> mustaq: Why is pointerevent_iframe-touch-action-none_touch.html correct? I don't quite understand why Chrome gets that pointercancel. Currently I think Firefox and Safari do the right thing. I could be missing something. https://wpt.fyi/results/pointerevents/pointerevent_iframe-touch-action-none_touch.html?label=master&label=experimental&aligned&q=pointerevent_iframe-touch-action-none_touch.html <plh> w3c/strategy#515 # UI events TF meeting Patrick: question we had is whether we still need/want UI events TF meeting every month? is there even still a UI events TF as such? Olli: what happens with the other events, like composition events? Olli: who is working on the remaining stuff? plh: you could go to web editing WG and say "should this group take it over?" and to the same that PEWG did for mouse/wheel plh: good thing is that it should be easier to do plh: for pointer events, do we still have dependency on UI events spec? if that spec disappears, would it affect PE? plh: are we still referencing UI events normatively? yes we are... plh: and there is still link to keyboard event olli: that should go to editing WG conceptually ACTION: Patrick to file an issue on PE about removing reliance on/reference to remaining UI events, we can flesh out further plh: mustaq you should move pointerlock-related things in UI events to the pointerlock spec <smaug> https://w3c.github.io/uievents/#external-pointerlock-algorithms ACTION: mustaq to look at moving/removing references to UI events related to pointerlock spec mustaq: these are the algos that Gary worked on ... i'll take a look at this and update pointerlock Summary of action items * Patrick to file an issue on PE about removing reliance on/reference to remaining UI events, we can flesh out further * mustaq to look at moving/removing references to UI events related to pointerlock spec -- 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, 6 May 2026 15:19:25 UTC