14:57:45 <RRSAgent> RRSAgent has joined #pointerevents
14:57:49 <RRSAgent> logging to https://www.w3.org/2024/04/10-pointerevents-irc
14:57:59 <Patrick_H_Lauke> Meeting: PEWG
14:58:04 <Patrick_H_Lauke> Chair: Patrick H. Lauke
14:58:12 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/6246bc85-4dae-43a8-a50c-9bc5a0829585/20240410T110000/
14:58:21 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
14:58:27 <Patrick_H_Lauke> ScribeNick: Patrick_H_Lauke
14:58:32 <Patrick_H_Lauke> present+
15:01:46 <Patrick_H_Lauke> present+ smaug
15:01:55 <Patrick_H_Lauke> present+ flackr
15:02:46 <Patrick_H_Lauke> TOPIC: Multi-pen support and persistent pointerId #353 https://github.com/w3c/pointerevents/issues/353
15:03:00 <Patrick_H_Lauke> Patrick: I see Olli made a few comments this morning on this
15:03:23 <Patrick_H_Lauke> Patrick: on the PR
15:03:38 <Patrick_H_Lauke> Olli: we shouldn't reserve any id for mouse ...
15:03:58 <Patrick_H_Lauke> Olli: don't think it says the really weird part, that on down event you may not get it. nobody expects that
15:04:09 <Patrick_H_Lauke> Rob: even the original example doesn't address that
15:04:19 <Patrick_H_Lauke> Rob: where they were taking the unique id from the down event
15:04:40 <Patrick_H_Lauke> Olli: because down is EXACTLY where i'd expect to get it, and use it from that point onwards
15:05:07 <Patrick_H_Lauke> Rob: I know i explicity asked them about whether or not it will be available on the down, and the answer was no/not necessarily, depending on hardware
15:05:30 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/pull/495
15:05:45 <Patrick_H_Lauke> Rob: I agree we need to make this a much more upfront warning for developers
15:06:13 <Patrick_H_Lauke> Olli: if it depends on a particular hardware or driver ... and is that behaviour only happening on windows?
15:06:25 <Patrick_H_Lauke> Rob: I think it may be down to some aspect of the communication model in hardware
15:07:06 <Patrick_H_Lauke> Rob: it MAY be that there's only windows devices that currently have this, but not hard to imagine same problem happening on other platforms once they add the hardware (e.g. adding support for a windows pen or similar)
15:08:14 <Patrick_H_Lauke> Patrick: so next step to comment further on PR and work with original submitter?
15:08:53 <Patrick_H_Lauke> Rob: yes, they're interested to see this through, so should be able to. there's a patch for Chromium in review right now to reflect these changes, so seem keen to get this shipped
15:09:09 <Patrick_H_Lauke> ACTION: continue discussion on https://github.com/w3c/pointerevents/pull/495
15:09:30 <Patrick_H_Lauke> TOPIC: Wide review for PE https://github.com/w3c/pointerevents/issues/482
15:12:55 <Patrick_H_Lauke> Patrick: I submitted most of the requests for review (a11y, i18n, TAG, i believe webapps too). still need to do a few more (privacy/security)
15:13:10 <Patrick_H_Lauke> Olli: how will they let us know if there are any problems?
15:13:17 <Patrick_H_Lauke> Patrick: they'll file issues in our repo
15:13:28 <Patrick_H_Lauke> ACTION: Patrick to file remaining requests for review
15:13:45 <Patrick_H_Lauke> TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 #445 https://github.com/w3c/pointerevents/issues/445
15:14:09 <Patrick_H_Lauke> Patrick: just a heartbeat - are there any blockers? how are we looking?
15:15:04 <Patrick_H_Lauke> Patrick: there's 4 (as the first one is for future change in touch action) https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+
15:15:41 <Patrick_H_Lauke> Rob: just looking through, don't think there's any blockers, just a question of time
15:16:04 <Patrick_H_Lauke> Olli: think there was something creaky with predicted events, you don't get those while testing because of limitations of test environment
15:16:25 <Patrick_H_Lauke> Rob: that's the one you were trying to write a test for and then got stuck?
15:16:34 <Patrick_H_Lauke> Olli: we may need to rely on coalesced events for now
15:16:55 <Patrick_H_Lauke> Olli: testing harness doesn't support, or might be on the browser side?
15:17:18 <Patrick_H_Lauke> Olli: don't think there's an API to tell if there ARE predicted events
15:17:40 <Patrick_H_Lauke> Rob: suppose in the cases where you give it a sequence of events, it COULD predict events that it still has to dispatch...
15:17:59 <Patrick_H_Lauke> Olli: and it wouldn't be what browsers actually do, because they get them from OS
15:18:17 <Patrick_H_Lauke> Patrick: could we just do manual tests then?
15:19:04 <Patrick_H_Lauke> Patrick: here's the visual demo that i made for predicted events https://patrickhlauke.github.io/touch/draw-predicted/index.html
15:21:04 <Patrick_H_Lauke> [discussion on how that could be used as basis for a manual test]
15:21:57 <Patrick_H_Lauke> ACTION: Olli to start looking at manual test for predicted events and check on other ongoing ones that were started
15:23:12 <Patrick_H_Lauke> rrsagent, set logs world-visible
15:23:18 <Patrick_H_Lauke> rrsagent, generate minutes
15:23:19 <RRSAgent> I have made the request to generate https://www.w3.org/2024/04/10-pointerevents-minutes.html Patrick_H_Lauke
15:23:56 <Patrick_H_Lauke> rrsagent, bye
15:23:56 <RRSAgent> I see 3 open action items saved in https://www.w3.org/2024/04/10-pointerevents-actions.rdf :
15:23:56 <RRSAgent> ACTION: continue discussion on https://github.com/w3c/pointerevents/pull/495 [1]
15:23:56 <RRSAgent>   recorded in https://www.w3.org/2024/04/10-pointerevents-irc#T15-09-09
15:23:56 <RRSAgent> ACTION: Patrick to file remaining requests for review [2]
15:23:56 <RRSAgent>   recorded in https://www.w3.org/2024/04/10-pointerevents-irc#T15-13-28
15:23:56 <RRSAgent> ACTION: Olli to start looking at manual test for predicted events and check on other ongoing ones that were started [3]
15:23:56 <RRSAgent>   recorded in https://www.w3.org/2024/04/10-pointerevents-irc#T15-21-57