W3C

– DRAFT –
PEWG

19 July 2023

Attendees

Present
flackr, mustaq, Patrick_H_Lauke, smaug
Regrets
-
Chair
Patrick H. Lauke
Scribe
Patrick H. Lauke, Patrick_H_Lauke

Meeting minutes

Meta-issue: update WPT to cover Pointer Events Level 3

w3c/pointerevents#445

Go overĀ https://github.com/w3c/pointerevents/issues?q=is%3Aclosed+label%3Aneeds-wpt+

Patrick: how are we doing with tests? any blockers/particularly tricky ones?

Olli: the secure context is a tricky one. do we want to change spec, or...

Mustaq: we have a counter in chrome for this, just waiting for data

w3c/pointerevents#318

Olli: do we have data, or do we need to wait until september?

Mustaq: we may have data from canary

Mustaq: maybe we can wait for first stable release

Olli: if we see already now that some sites are already using it we can make a decision

Mustaq: in chrome 117, goes stable next month

Mustaq: we can wait for stable data, or see what we have so far

Olli: where do we get telemetry data for chrome... is it chromestatus?

Rob: it is on chromestatus, it's in the stats on the left

Rob: maybe it's not there yet...

Patrick: yeah i don't see it (getCoealescedInSecureContext ?)

Rob: not seeing it

<mustaq> "GetCoalescedEventsInInsecureContext" should appear there.

https://chromestatus.com/metrics/feature/popularity

Mustaq: let's look at it offline, need to get back to it in two weeks to get data

Rob: I think the fact it's not there means it hasn't happened (and not that it hasn't received data yet)

Mustaq: beta in one month, stable in two months

Olli: can wait and see what data we have

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

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

Patrick: I'll put myself down to make PR for the change now

ACTION: Patrick to write PR to address w3c/pointerevents#472

Patrick: will that then make the WPT easier to fix?

Rob: it would actually be easier if we completely removed the methods...

Olli: but should be feasible either way

Olli: I can write a new WPT for that if you do the PR Patrick

Patrick: Sounds good

ACTION: Olli to write WPT once Patrick's PR merged

TPAC demo video

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]

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)

ACTION: Patrick to create "What's new in PE Level 3" video

Patrick: meanwhile, thank you all as ever

Summary of action items

  1. Patrick to write PR to address w3c/pointerevents#472
  2. Olli to write WPT once Patrick's PR merged
  3. Patrick to create "What's new in PE Level 3" video
Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).

Diagnostics

Maybe present: Olli, Patrick, Rob

All speakers: Mustaq, Olli, Patrick, Rob

Active on IRC: mustaq, Patrick_H_Lauke