16:00:58 <RRSAgent> RRSAgent has joined #pointerevents
16:01:02 <RRSAgent> logging to https://www.w3.org/2024/02/14-pointerevents-irc
16:01:07 <Patrick_H_Lauke> Meeting: PEWG
16:01:22 <smaug> present+
16:01:23 <Patrick_H_Lauke> Chair: Patrick H. Lauke
16:01:27 <flackr> present+
16:03:19 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/6246bc85-4dae-43a8-a50c-9bc5a0829585/20240214T110000/
16:03:23 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
16:03:29 <Patrick_H_Lauke> ScribeNick: Patrick_H_Lauke
16:03:32 <Patrick_H_Lauke> present+
16:03:47 <mustaq> present+
16:04:27 <Patrick_H_Lauke> TOPIC: Multi-pen support and persistent pointerId #353 https://github.com/w3c/pointerevents/issues/353
16:04:27 <Patrick_H_Lauke> ACTION: Rob to speak to Microsoft about using a more generalised structure for the deviceId info
16:04:57 <flackr> https://groups.google.com/a/chromium.org/g/blink-dev/c/3eU-AHH8x4k/m/oCO7WKt1AAAJ?utm_medium=email&utm_source=footer
16:06:58 <Patrick_H_Lauke> Rob: asked questions in the intent thread to bring back to discussion
16:07:27 <Patrick_H_Lauke> Rob: i think there's answers here, but we need to figure out WHEN the field is set. value is pseudorandom, equivalent to pointerid, but should it be set for cases where multiple pointers are set on same device (e.g. hand with different touches). should probably only have it when the system itself can differentiate when it's an input that only has one pointer
16:07:57 <Patrick_H_Lauke> Olli: what is a device? it's kind of vague. maybe all touches are the same, as they have different pointerid
16:08:32 <Patrick_H_Lauke> Rob: yeah, you can use a combination of pointerid and deviceid, to differentiate
16:08:32 <Patrick_H_Lauke> Rob: i think that's how it's coded in chromium ...
16:08:43 <Patrick_H_Lauke> Rob: but this needs to be called out / spec'd
16:09:03 <Patrick_H_Lauke> Rob: explicitly asked in the latest for them to comment back on thread
16:10:05 <Patrick_H_Lauke> Rob: don't have concerns about deviceProperties as the name, seems reasonable. can always change later...
16:10:42 <Patrick_H_Lauke> Rob: i think we have enough to move forward on this
16:11:38 <Patrick_H_Lauke> Olli: will then need to see how this affects click event
16:11:45 <Patrick_H_Lauke> Olli: what happens if triggered by keyboard
16:11:46 <Patrick_H_Lauke> Rob: probably same logic as we do for keyboard...
16:11:49 <Patrick_H_Lauke> Olli: pointerid is -1 for keyboard
16:14:31 <Patrick_H_Lauke> TOPIC: Update https://github.com/web-platform-tests/wpt/blob/master/pointerevents/META.yml #498 https://github.com/w3c/pointerevents/issues/498
16:15:12 <smaug> https://github.com/web-platform-tests/interop/issues/628
16:15:14 <Patrick_H_Lauke> Olli: posted this, will be updated automatically
16:15:27 <Patrick_H_Lauke> TOPIC: interop pointer events issue
16:15:41 <Patrick_H_Lauke> Olli: test change proposal for pointer events https://github.com/web-platform-tests/interop/issues/628
16:16:23 <Patrick_H_Lauke> Mustaq: proposed changes...
16:17:28 <Patrick_H_Lauke> Olli: items that don't currently have include/exclude ... should I go in to change them in spreadsheet? just comment there?
16:17:44 <Patrick_H_Lauke> Mustaq: if you make changes in spreadsheet, then point it out in the comment on the issue there, so we can sync
16:17:57 <Patrick_H_Lauke> Mustaq: one concern may be number of tests we want to include. too many?
16:18:21 <Patrick_H_Lauke> Olli: think most of them are fine, some weren't in GH at all because of the issues with interop23
16:18:55 <Patrick_H_Lauke> TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 #445 https://github.com/w3c/pointerevents/issues/445
16:21:11 <Patrick_H_Lauke> Mustaq: got rid of one issue, got question about 477
16:21:45 <Patrick_H_Lauke> Mustaq: https://github.com/w3c/pointerevents/issues/477 question if these relate to shadow DOM
16:22:22 <Patrick_H_Lauke> Olli: definitely added tests for shadow DOM for various things
16:22:26 <mustaq> https://github.com/web-platform-tests/interop/issues/380#issuecomment-1913786467
16:22:51 <mustaq> Do these two tests cover the missing shadow dom cases for #477?
16:24:20 <mustaq> https://www.irccloud.com/pastebin/taCxoszU/
16:24:36 <Patrick_H_Lauke> pointerevent_pointer_boundary_events_after_removing_last_over_element.html
16:24:53 <Patrick_H_Lauke> To be precise: the second promise_test
16:25:02 <mustaq> https://github.com/web-platform-tests/wpt/blob/master/pointerevents/pointerevent_pointer_boundary_events_after_removing_last_over_element.html
16:25:14 <Patrick_H_Lauke> Rob: not sure if either of those deals with slotted element
16:25:35 <Patrick_H_Lauke> Rob: because one of the cases in 477 we called out was if you have slotted...
16:25:51 <Patrick_H_Lauke> Olli: maybe we need to point out in issue that this needs to also deal with the slotted case
16:29:27 <Patrick_H_Lauke> Patrick: random question ... do we know if coalesced and predicted events have actually started to be used in the wild?
16:29:42 <flackr> getPredictedEvents use counter https://chromestatus.com/metrics/feature/timeline/popularity/2971
16:30:16 <mustaq> getCoalescedEvents use counter: https://chromestatus.com/metrics/feature/timeline/popularity/4598
16:31:46 <mustaq> Correction: the lat link is only for insecure context usage
16:32:37 <Patrick_H_Lauke> rrsagent, set logs world-visible
16:32:41 <Patrick_H_Lauke> rrsagent, generate minutes
16:32:42 <RRSAgent> I have made the request to generate https://www.w3.org/2024/02/14-pointerevents-minutes.html Patrick_H_Lauke
16:50:28 <Patrick_H_Lauke> rrsagent, bye
16:50:28 <RRSAgent> I see 1 open action item saved in https://www.w3.org/2024/02/14-pointerevents-actions.rdf :
16:50:28 <RRSAgent> ACTION: Rob to speak to Microsoft about using a more generalised structure for the deviceId info [1]
16:50:28 <RRSAgent>   recorded in https://www.w3.org/2024/02/14-pointerevents-irc#T16-04-27-1