14:51:42 <RRSAgent> RRSAgent has joined #pointerevents
14:51:47 <RRSAgent> logging to https://www.w3.org/2024/08/14-pointerevents-irc
14:52:46 <Patrick_H_Lauke> Meeting: PEWG
14:52:51 <Patrick_H_Lauke> Chair: Patrick H. Lauke
14:53:05 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/16b7312b-55ac-4645-8312-0d8103f75519/20240814T110000/
14:53:15 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
14:53:21 <Patrick_H_Lauke> ScribeNick: Patrick_H_Lauke
14:53:23 <Patrick_H_Lauke> present+
14:54:03 <Patrick_H_Lauke> regrets+ smaug
15:05:07 <flackr> flackr has joined #pointerevents
15:05:08 <Patrick_H_Lauke> present+ flackr
15:05:28 <Patrick_H_Lauke> TOPIC: ‘Logical’ values for the ‘touch-action’ property #505
15:05:28 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/issues/505
15:06:46 <Patrick_H_Lauke> Patrick: as discussed in last meeting, i left comment on that issue about our decision to defer to Level 4
15:06:54 <Patrick_H_Lauke> TOPIC: Add persistentDeviceId to PointerEvent #495
15:06:54 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/pull/495
15:07:11 <Patrick_H_Lauke> Patrick: as discussed in our last meeting, I've now merged this into Level 4 / gh-pages branch
15:07:32 <Patrick_H_Lauke> TOPIC: Triage unlabelled issues https://github.com/w3c/pointerevents/issues
15:09:02 <Patrick_H_Lauke> Patrick: want to see if anything is urgent and needs to be added to Level 3, or if we can defer
15:10:04 <Patrick_H_Lauke> Rob: the issues asking for clarification may be things we want to do for v3, but need time to review
15:10:18 <Patrick_H_Lauke> ACTION: review any unlabelled issues and mark them as v3 or future
15:10:42 <Patrick_H_Lauke> TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 #445 https://github.com/w3c/pointerevents/issues/445
15:10:59 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+
15:11:12 <Patrick_H_Lauke> Rob: I have something started
15:11:16 <flackr> https://chromium-review.googlesource.com/c/chromium/src/+/5759832
15:11:50 <Patrick_H_Lauke> Rob: discovered that Chrome at least doesn't seem to match spec behaviour. matches in one direction but not other
15:12:18 <Patrick_H_Lauke> Rob: spec seems to imply that you can never capture a pointer if it's not in the active document. In chrome the capture works in one direction but not the other
15:12:57 <Patrick_H_Lauke> Rob: haven't checked whether Firefox or Safari do the "correct" thing yet. depending on the outcome, we can come back and debate if the spec needs to allow capturing in one direction but not other
15:13:46 <Patrick_H_Lauke> Rob: if i remember correctly, the issue I found was that if you try to set capture into an inner frame, Chrome allows it, but by spec we shouldn't
15:14:35 <Patrick_H_Lauke> Rob: i'll post a repro example to the issue, then we can debate (and get results from Safari/Firefox to inform discussion)
15:14:38 <Patrick_H_Lauke> ACTION: futher exploration needed
15:14:49 <Patrick_H_Lauke> TOPIC: Level 3 and Level 4
15:15:16 <Patrick_H_Lauke> Patrick: I've gone ahead and followed PLH suggestion to set up a Level 3 branch, and treat gh-pages as Level 4
15:15:59 <Patrick_H_Lauke> ACTION: Patrick to catch up with PLH to make sure the new branch structure doesn't auto-publish to wrong place
15:16:33 <flackr> In https://w3c.github.io/pointerevents/#setting-pointer-capture the failure when trying to capture to a different document is completely silent - no exception thrown
15:16:45 <flackr> > If the pointer is not in the active buttons state or the element's node document is not the active document of the pointer, then terminate these steps.
15:17:32 <Patrick_H_Lauke> Patrick: so we want to make a change to spec anyway to clarify / don't keep failure silent and instead throw error
15:18:47 <Patrick_H_Lauke> Patrick: I can see how you'd possibly want to allow capturing down (from parent document into frame) but not other way around, as it could be a third party script that should not be allowed...
15:18:57 <Patrick_H_Lauke> Rob: keep in mind it can't be cross-origin
15:35:29 <Patrick_H_Lauke> [Rob gave a very brief additional context/discussion on the thinking behind https://github.com/w3c/pointerevents/issues/512 to gauge interest/use cases. We will discuss this further in future meeting]
15:35:42 <Patrick_H_Lauke> RSSAgent, set logs world-visible
15:35:58 <Patrick_H_Lauke> regrets+ mustaq
15:36:13 <Patrick_H_Lauke> RRSAgent, generate minutes
15:36:14 <RRSAgent> I have made the request to generate https://www.w3.org/2024/08/14-pointerevents-minutes.html Patrick_H_Lauke
15:37:03 <Patrick_H_Lauke> RRSAgent, set logs world-visible
15:37:23 <Patrick_H_Lauke> rrsagent, bye
15:37:23 <RRSAgent> I see 3 open action items saved in https://www.w3.org/2024/08/14-pointerevents-actions.rdf :
15:37:23 <RRSAgent> ACTION: review any unlabelled issues and mark them as v3 or future [1]
15:37:23 <RRSAgent>   recorded in https://www.w3.org/2024/08/14-pointerevents-irc#T15-10-18
15:37:23 <RRSAgent> ACTION: futher exploration needed [2]
15:37:23 <RRSAgent>   recorded in https://www.w3.org/2024/08/14-pointerevents-irc#T15-14-38
15:37:23 <RRSAgent> ACTION: Patrick to catch up with PLH to make sure the new branch structure doesn't auto-publish to wrong place [3]
15:37:23 <RRSAgent>   recorded in https://www.w3.org/2024/08/14-pointerevents-irc#T15-15-59