15:02:19 <RRSAgent> RRSAgent has joined #pointerevents
15:02:23 <RRSAgent> logging to https://www.w3.org/2025/07/16-pointerevents-irc
15:02:24 <Patrick_H_Lauke> Meeting: PEWG
15:02:27 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/66591f6b-6694-4f90-b23d-bf8f1b9dda8a/20250716T110000/
15:02:34 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
15:02:42 <Patrick_H_Lauke> ScribeNick: Patrick_H_Lauke
15:02:46 <Patrick_H_Lauke> Chair: Patrick H. Lauke
15:02:48 <Patrick_H_Lauke> present+
15:02:52 <Patrick_H_Lauke> present+ mustaq
15:02:56 <Patrick_H_Lauke> present+ flackr
15:03:22 <Patrick_H_Lauke> TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3
15:03:29 <Patrick_H_Lauke> Patrick: https://github.com/w3c/pointerevents/issues/445 / https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+
15:04:19 <Patrick_H_Lauke> Looks like we've got none left...
15:04:59 <Patrick_H_Lauke> last one we had was https://github.com/w3c/pointerevents/issues/509 which seems to have been resolved now
15:05:51 <Patrick_H_Lauke> So unless there's anything else that was missed out that we think desperately needs a wpt, think we're in a good spot
15:07:07 <Patrick_H_Lauke> So at this stage, it would be good in our respective browser implementations if we could go through the WPTs that are now complete, and see how we're doing
15:07:30 <Patrick_H_Lauke> And if things fail, working out if it's features/bugs that are planned to be addressed or not
15:07:51 <Patrick_H_Lauke> Next step I think was for Philippe (plh) to collate things based on the WPTs for implementation report
15:08:31 <Patrick_H_Lauke> ACTION: review the WPT results at this stage, investigate any failures
15:08:55 <Patrick_H_Lauke> TOPIC: Any particular old or new issues that we want to start thinking about/tackling?
15:09:04 <mustaq> https://github.com/w3c/pointerevents/issues/507
15:09:44 <Patrick_H_Lauke> mustaq: I would love to close out https://github.com/w3c/pointerevents/issues/507 ... but we'd need somebody from Firefox to check in, but feel free to comment on the issue
15:10:45 <Patrick_H_Lauke> We have 32 issues at this stage (just closed https://github.com/w3c/pointerevents/issues/445 as we've sorted WPTs)
15:11:13 <mustaq> https://github.com/w3c/pointerevents/issues/542
15:14:22 <Patrick_H_Lauke> [mustaq explains what the intention is with drifting clicks]
15:15:12 <Patrick_H_Lauke> Patrick: what i do hate, if this is the same: say you have a dialog, inside it there's a text field; i highlight the content by dragging my mouse, but accidentally end up finishing just outside of the dialog, and it auto-closes. i didn't intend that...
15:15:35 <Patrick_H_Lauke> mustaq: we don't have that problem for touch, as a click is not sent when there's movement
15:16:29 <Patrick_H_Lauke> Rob: i'm not sure i'm a fan of the thinking that click should be sent for drifting pointer - as on touch it's the way for a user to change their mind
15:17:10 <Patrick_H_Lauke> Rob: maybe if we found a way of declaring/stating that there is a boundary, so if you stay within it it still counts as click, but otherwise don't fire click
15:17:18 <Patrick_H_Lauke> Rob: something to say this is a clickable thing
15:17:34 <Patrick_H_Lauke> Rob: "click boundary" as a strawman term
15:18:23 <Patrick_H_Lauke> mustaq: might have something we can do with target...
15:20:05 <Patrick_H_Lauke> mustaq: maybe we can do something where drifting click can work for mouse, but leave touch as is
15:21:16 <Patrick_H_Lauke> Rob: we also have implicit capture, that brings up difference between mouse click and touch click
15:21:51 <Patrick_H_Lauke> Rob: not sure what Joey's expectation is specifically, might need to dig in a bit more
15:23:07 <Patrick_H_Lauke> Patrick: to be clear, that problem I have been seeing is usually in a JavaScript-y implementation, not the current native <dialog>
15:27:31 <Patrick_H_Lauke> Patrick: if we want to explore more dramatic changes (like making touch click work more like mouse click), we can start that conversation if we're aiming that for PE Level 4 - gives us time to explore potential compat dangers etc
15:28:05 <Patrick_H_Lauke> mustaq: let me file a new issue about the touch case, because the spec doesn't say specifically what happens, so not easy
15:28:34 <Patrick_H_Lauke> Patrick: possibly an easy one - this issue https://github.com/w3c/pointerevents/issues/543
15:30:13 <Patrick_H_Lauke> We originally didn't include gestures for IPR concerns...but maybe the time is right now to broach the subject?
15:30:21 <Patrick_H_Lauke> Rob: if not our group, then who?
15:31:02 <Patrick_H_Lauke> mustaq: maybe we can start putting feelers out
15:31:14 <Patrick_H_Lauke> This would be perfect for a hallway conversation at TPAC
15:36:38 <Patrick_H_Lauke> mustaq: let's keep #543 open as an initial place for discussion
15:36:49 <Patrick_H_Lauke> Thank you all, we'll reconvene in two weeks' time
15:36:57 <Patrick_H_Lauke> rrsagent, set logs world-visible
15:37:04 <Patrick_H_Lauke> rrsagent, generate minutes
15:37:05 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/16-pointerevents-minutes.html Patrick_H_Lauke
15:39:23 <Patrick_H_Lauke> rrsagent, bye
15:39:23 <RRSAgent> I see 1 open action item saved in https://www.w3.org/2025/07/16-pointerevents-actions.rdf :
15:39:23 <RRSAgent> ACTION: review the WPT results at this stage, investigate any failures [1]
15:39:23 <RRSAgent>   recorded in https://www.w3.org/2025/07/16-pointerevents-irc#T15-08-31