- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 26 Feb 2025 16:36:05 +0000
- To: public-pointer-events@w3.org
Dear all, the minutes from today's meeting are at https://www.w3.org/2025/02/26-pointerevents-minutes.html and copied below: PEWG 26 February 2025 Agenda: https://www.w3.org/events/meetings/66591f6b-6694-4f90-b23d-bf8f1b9dda8a/20250226T110000/ IRC log: https://www.w3.org/2025/02/26-pointerevents-irc Attendees Present: adettenb, flackr, mustaq, Patrick_H_Lauke Regrets: smaug Chair: Patrick H. Lauke Scribe: Patrick H. Lauke * v3-blocking issues https://github.com/w3c/pointerevents/issues?q=is%3Aissue%20state%3Aopen%20label%3Av3-blocking * Meta-issue: update WPT to cover Pointer Events Level 3 #445 w3c/pointerevents#445 * scoping `handwriting` to scrollable vs document w3c/pointerevents#516 * AOB # v3-blocking issues https://github.com/w3c/pointerevents/issues?q=is%3Aissue%20state%3Aopen%20label%3Av3-blocking Patrick: so only one actually left w3c/pointerevents#504 mustaq: I forgot about this one, but will send a PR in the next few days ACTION: mustaq to address #504 # Meta-issue: update WPT to cover Pointer Events Level 3 #445 w3c/pointerevents#445 Patrick: not looking bad - here's the last remaining ones https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+ mustaq: one has v3-blocking, one has v3, what's difference? Patrick: those labels are left over from when we did the actual PRs. don't see "blocking" on WPT ones as meaning we can't go to v3 without the tests, but would be good to get full coverage soon Patrick: obviously ignore the one with "future" as that's not immediately relevant for v3 mustaq: i can take a look at #534 w3c/pointerevents#534 Patrick: that leaves us with w3c/pointerevents#513 and w3c/pointerevents#509 Patrick: do those look ... doable? need some discussion? adettenb: for #513 is looks like there hasn't been an event, and they'd like it to be 0 or 1? mustaq: if you look at the pull request ... flackr: at high level it's about testing button on a click adettenb: I can take a look at that one mustaq: there's a test "click is a pointer event", that should have something, but might not test all properties <mustaq> pointerevent_click_is_a_pointerevent.html Patrick: I might see if Olli can take care of #509 as he's been chatting with Masayuki about it ACTION: WPT work - mustaq to look at #534, adettenb to look at #513, smaug to look at #509 # scoping `handwriting` to scrollable vs document w3c/pointerevents#516 adettenb: I wanted to understand more about scoping the attribute in certain contexts. wasn't sure if the approach taken in the PR (similar to pan) is appropriate? wonder why it should be scope to a scollable rather than higher level like document flackr: scoped possibly not quite right... getting reenabled. decided to do this for scrolling - is handwriting different? maybe... flackr: one of the nice things: if we did this, addresses Patrick's concern that more likely for legacy content you'll get the expected behaviour (as no sites have opted in for handwriting anywhere at this point, and it would be suppressed in all cases until authors actively enable it) flackr: less of a compat risk flackr: i think though probably innerdocuments should get it reenabled adettenb: like iframes? yes. they would be considered scrollables though right? flackr: would need special case. currently it reenables panning because they're scrollable though, yes adettenb: for iframe ... would it be possible to be disabled from outside of iframe? top level body vs on iframe itself, for instance? adettenb: not tested what happens in these scenarios with panning, so not sure if this would affect suggested enabling of handwriting flackr: there *are* better ways to prevent things happening on inner documents flackr: not clear though. outer document *could* disable inner document, but outer document still wouldn't see the events to do anything useful with them Patrick: does that answer your concerns so far? adettenb: yes, makes the rationale a bit clearer. will be good once we get some metrics # AOB Patrick: i went through and updated v3 https://www.w3.org/TR/pointerevents3/ Patrick: cherry-picking any changes we made on gh-pages that were still relevant for v3 Patrick: for the curious https://github.com/w3c/pointerevents/pulls?q=is%3Apr+is%3Aclosed Patrick: it's the ones i tagged as port-to-v3 <mustaq> Interop 2025 Pointer/Mouse events: <mustaq> https://wpt.fyi/results/?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2023-events Patrick: also updated acknowledgements and revision history, so think v3 is now as ready as it can be Patrick: I will see about finally getting v3 onto the proper REC track now that we've weeded out the last remaining gnarly edge-case things we wanted to tackle for this version. Thanks as ever to everybody, we'll catch up again in 2 weeks' time # Summary of action items * mustaq to address #504 * WPT work - mustaq to look at #534, adettenb to look at #513, smaug to look at #509 -- 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 February 2025 16:36:14 UTC