16:01:25 RRSAgent has joined #pointerevents 16:01:29 logging to https://www.w3.org/2025/02/26-pointerevents-irc 16:02:36 Meeting: PEWG 16:02:40 Chair: Patrick H. Lauke 16:02:44 Scribe: Patrick H. Lauke 16:02:46 adettenb has joined #pointerevents 16:03:11 ScribeNick: Patrick_H_Lauke 16:03:27 Agenda: https://www.w3.org/events/meetings/66591f6b-6694-4f90-b23d-bf8f1b9dda8a/20250226T110000/ 16:03:38 present+ Patrick_H_Lauke 16:03:42 present+ adettenb 16:03:47 present+ mustaq 16:04:00 present+ flackr 16:04:24 regrets+ smaug 16:04:45 + https://github.com/w3c/pointerevents/issues/516 16:04:45 (for scoping `handwriting` to scrollable vs document) 16:05:37 TOPIC: v3-blocking issues https://github.com/w3c/pointerevents/issues?q=is%3Aissue%20state%3Aopen%20label%3Av3-blocking 16:06:11 flackr has joined #pointerevents 16:06:17 Patrick: so only one actually left https://github.com/w3c/pointerevents/issues/504 16:06:37 mustaq: I forgot about this one, but will send a PR in the next few days 16:06:48 ACTION: mustaq to address #504 16:07:07 TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 #445 https://github.com/w3c/pointerevents/issues/445 16:07:34 Patrick: not looking bad - here's the last remaining ones https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+ 16:09:03 mustaq: one has v3-blocking, one has v3, what's difference? 16:09:36 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 16:09:49 Patrick: obviously ignore the one with "future" as that's not immediately relevant for v3 16:11:12 mustaq: i can take a look at #534 https://github.com/w3c/pointerevents/issues/534 16:11:37 Patrick: that leaves us with https://github.com/w3c/pointerevents/issues/513 and https://github.com/w3c/pointerevents/issues/509 16:12:38 Patrick: do those look ... doable? need some discussion? 16:12:58 adettenb: for #513 is looks like there hasn't been an event, and they'd like it to be 0 or 1? 16:14:01 mustaq: if you look at the pull request ... 16:14:19 flackr: at high level it's about testing button on a click 16:14:30 adettenb: I can take a look at that one 16:14:47 mustaq: there's a test "click is a pointer event", that should have something, but might not test all properties 16:15:01 pointerevent_click_is_a_pointerevent.html 16:15:34 Patrick: I might see if Olli can take care of #509 as he's been chatting with Masayuki about it 16:16:10 ACTION: WPT work - mustaq to look at #534, adettenb to look at #513, smaug to look at #509 16:16:58 TOPIC: scoping `handwriting` to scrollable vs document https://github.com/w3c/pointerevents/issues/516 16:18:33 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 16:19:10 flackr: scoped possibly not quite right... getting reenabled. decided to do this for scrolling - is handwriting different? maybe... 16:20:12 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) 16:20:20 flackr: less of a compat risk 16:20:49 flackr: i think though probably innerdocuments should get it reenabled 16:21:04 adettenb: like iframes? yes. they would be considered scrollables though right? 16:21:22 flackr: would need special case. currently it reenables panning because they're scrollable though, yes 16:21:51 adettenb: for iframe ... would it be possible to be disabled from outside of iframe? top level body vs on iframe itself, for instance? 16:22:32 adettenb: not tested what happens in these scenarios with panning, so not sure if this would affect suggested enabling of handwriting 16:22:46 flackr: there *are* better ways to prevent things happening on inner documents 16:23:49 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 16:24:54 Patrick: does that answer your concerns so far? 16:25:09 adettenb: yes, makes the rationale a bit clearer. will be good once we get some metrics 16:25:45 TOPIC: AOB 16:25:55 Patrick: i went through and updated v3 https://www.w3.org/TR/pointerevents3/ 16:26:26 Patrick: cherry-picking any changes we made on gh-pages that were still relevant for v3 16:26:37 Patrick: for the curious https://github.com/w3c/pointerevents/pulls?q=is%3Apr+is%3Aclosed 16:26:49 Patrick: it's the ones i tagged as port-to-v3 16:28:01 Interop 2025 Pointer/Mouse events: 16:28:02 https://wpt.fyi/results/?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2023-events 16:28:36 Patrick: also updated acknowledgements and revision history, so think v3 is now as ready as it can be 16:30:59 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 16:31:06 rrsagent, make logs world-visible 16:31:12 rrsagent, generate minutes 16:31:13 I have made the request to generate https://www.w3.org/2025/02/26-pointerevents-minutes.html Patrick_H_Lauke 16:37:39 rrsagent, bye 16:37:39 I see 2 open action items saved in https://www.w3.org/2025/02/26-pointerevents-actions.rdf : 16:37:39 ACTION: mustaq to address #504 [1] 16:37:39 recorded in https://www.w3.org/2025/02/26-pointerevents-irc#T16-06-48 16:37:39 ACTION: WPT work - mustaq to look at #534, adettenb to look at #513, smaug to look at #509 [2] 16:37:39 recorded in https://www.w3.org/2025/02/26-pointerevents-irc#T16-16-10