14:54:35 <RRSAgent> RRSAgent has joined #pointerevents
14:54:39 <RRSAgent> logging to https://www.w3.org/2023/07/19-pointerevents-irc
14:54:52 <Patrick_H_Lauke> Meeting: PEWG
14:55:02 <Patrick_H_Lauke> Chair: Patrick H. Lauke
14:55:13 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/6246bc85-4dae-43a8-a50c-9bc5a0829585/20230719T110000/
14:55:24 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
14:55:32 <Patrick_H_Lauke> ScribeNick: Patrick_H_Lauke
14:55:33 <Patrick_H_Lauke> present+
14:59:37 <Patrick_H_Lauke> present+ smaug
15:03:14 <flackr> flackr has joined #pointerevents
15:03:55 <Patrick_H_Lauke> present+ flackr
15:03:55 <Patrick_H_Lauke> present+ mustaq
15:04:53 <Patrick_H_Lauke> TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3
15:04:59 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/issues/445
15:04:59 <Patrick_H_Lauke> Go over https://github.com/w3c/pointerevents/issues?q=is%3Aclosed+label%3Aneeds-wpt+
15:05:36 <Patrick_H_Lauke> Patrick: how are we doing with tests? any blockers/particularly tricky ones?
15:05:51 <Patrick_H_Lauke> Olli: the secure context is a tricky one. do we want to change spec, or...
15:06:06 <Patrick_H_Lauke> Mustaq: we have a counter in chrome for this, just waiting for data
15:06:19 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/pull/318
15:06:47 <Patrick_H_Lauke> Olli: do we have data, or do we need to wait until september?
15:06:56 <Patrick_H_Lauke> Mustaq: we may have data from canary
15:07:13 <Patrick_H_Lauke> Mustaq: maybe we can wait for first stable release
15:07:49 <Patrick_H_Lauke> Olli: if we see already now that some sites are already using it we can make a decision
15:08:42 <Patrick_H_Lauke> Mustaq: in chrome 117, goes stable next month
15:09:03 <Patrick_H_Lauke> Mustaq: we can wait for stable data, or see what we have so far
15:09:24 <Patrick_H_Lauke> Olli: where do we get telemetry data for chrome... is it chromestatus?
15:09:38 <Patrick_H_Lauke> Rob: it is on chromestatus, it's in the stats on the left
15:10:34 <Patrick_H_Lauke> Rob: maybe it's not there yet...
15:10:48 <Patrick_H_Lauke> Patrick: yeah i don't see it (getCoealescedInSecureContext ?)
15:11:11 <Patrick_H_Lauke> Rob: not seeing it
15:11:16 <mustaq> "GetCoalescedEventsInInsecureContext" should appear there.
15:11:43 <Patrick_H_Lauke> https://chromestatus.com/metrics/feature/popularity
15:12:35 <Patrick_H_Lauke> Mustaq: let's look at it offline, need to get back to it in two weeks to get data
15:12:55 <Patrick_H_Lauke> Rob: I think the fact it's not there means it hasn't happened (and not that it hasn't received data yet)
15:13:08 <Patrick_H_Lauke> Mustaq: beta in one month, stable in two months
15:13:17 <Patrick_H_Lauke> Olli: can wait and see what data we have
15:18:05 <Patrick_H_Lauke> Patrick: so what do we want to do...make #472 v3 blocking and wait for data from counter? Could get PRs ready either way and then merge as soon as we have data
15:19:01 <Patrick_H_Lauke> Olli: or we can land a PR *now* to return empty array on non-secure, and make change later (depending on data) to completely remove it
15:19:50 <Patrick_H_Lauke> Patrick: I'll put myself down to make PR for the change now
15:20:08 <Patrick_H_Lauke> ACTION: Patrick to write PR to address https://github.com/w3c/pointerevents/issues/472
15:20:47 <Patrick_H_Lauke> Patrick: will that then make the WPT easier to fix?
15:20:59 <Patrick_H_Lauke> Rob: it would actually be easier if we completely removed the methods...
15:21:14 <Patrick_H_Lauke> Olli: but should be feasible either way
15:21:25 <Patrick_H_Lauke> Olli: I can write a new WPT for that if you do the PR Patrick
15:21:28 <Patrick_H_Lauke> Patrick: Sounds good
15:21:40 <Patrick_H_Lauke> ACTION: Olli to write WPT once Patrick's PR merged
15:27:18 <Patrick_H_Lauke> TOPIC: TPAC demo video
15:29:22 <Patrick_H_Lauke> Patrick: just a heads-up, you probably saw, I put myself down to make a short video for TPAC covering pointerrawmove, getCoalescedEvents() and getPredictedEvents(), azimuthAngle/altitudeAngle (excuse to show off the webGL stylus demo again), mention that click/auxclick/contextmenu are now PEs so can now see what input caused a particular action there too (taking place of the old inputDeviceCapabilities approach). deadline[CUT]
15:29:22 <Patrick_H_Lauke> ng video done is 30 August, don't foresee any major problems in getting it done for then, already have most demos in place (will tweak slightly)
15:30:43 <Patrick_H_Lauke> ACTION: Patrick to create "What's new in PE Level 3" video
15:31:01 <Patrick_H_Lauke> Patrick: meanwhile, thank you all as ever
15:31:07 <Patrick_H_Lauke> RRSAgent, set logs world-visible
15:31:13 <Patrick_H_Lauke> RRSAgent, generate minutes
15:31:14 <RRSAgent> I have made the request to generate https://www.w3.org/2023/07/19-pointerevents-minutes.html Patrick_H_Lauke
15:31:32 <Patrick_H_Lauke> RRSAgent, set logs world-visible
15:31:45 <Patrick_H_Lauke> RRSAgent, bye
15:31:45 <RRSAgent> I see 3 open action items saved in https://www.w3.org/2023/07/19-pointerevents-actions.rdf :
15:31:45 <RRSAgent> ACTION: Patrick to write PR to address https://github.com/w3c/pointerevents/issues/472 [1]
15:31:45 <RRSAgent>   recorded in https://www.w3.org/2023/07/19-pointerevents-irc#T15-20-08
15:31:45 <RRSAgent> ACTION: Olli to write WPT once Patrick's PR merged [2]
15:31:45 <RRSAgent>   recorded in https://www.w3.org/2023/07/19-pointerevents-irc#T15-21-40
15:31:45 <RRSAgent> ACTION: Patrick to create "What's new in PE Level 3" video [3]
15:31:45 <RRSAgent>   recorded in https://www.w3.org/2023/07/19-pointerevents-irc#T15-30-43