– DRAFT –
PEWG

Meta-issue: update WPT to cover Pointer Events Level 3 w3c/pointerevents#445 / https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+

<adettenb> https://chromium-review.googlesource.com/c/chromium/src/+/6440250

Adam: link to changes for WPT I had

Outstanding we have: https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+

Patrick: so the one you sent Adam is for the button property? w3c/pointerevents#513

Adam: yes, found a test that was similar, so used that. also had to change how the test was running on load, was having trouble finding the method ... was resolving before finished loading

Patrick: looking at w3c/pointerevents#534 i think mustaq wanted to do some more on that

Olli: Masayuki has been working around pointerrawupdate, so let me check if he's added anything

Olli: i think we have one pointerrawupdate related test missing

Patrick: yeah this one w3c/pointerevents#509

Patrick: and one about mouse w3c/pointerevents#529

Patrick: so would be good to get tests at least. don't think they need to all pass yet for going onto REC track, but ideally yes to exit

<smaug> https://wpt.fyi/results/pointerevents?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2023-events

Olli: people might still be busy at the moment with interop issues

Patrick: understandable. would still be good to get at least prototypical tests set up

ACTION: review outstanding "needs-WPT" issues

Adam: blinkon is also happening

<smaug> https://wpt.fyi/results/pointerevents?label=master&label=experimental

Olli: do we need at least one implementation that passes ALL tests?

Olli: there are still some tests that seem to fail in all browser

Patrick: I will check with Philippe what the deal is

ACTION: Patrick to check with PLH about need for a fully compliant implementation or not to *enter* / *exit* CR/REC track

Patrick: keeping it short and sweet today then. We'll reconvene in 2 weeks' time