14:45:36 RRSAgent has joined #pointerevents 14:45:40 logging to https://www.w3.org/2026/01/28-pointerevents-irc 14:45:40 Meeting: PEWG 14:45:44 Chair: Patrick H. Lauke 14:45:48 Scribe: Patrick H. Lauke 14:45:55 ScribeNick: Patrick_H_Lauke 14:46:33 Agenda: https://www.w3.org/events/meetings/bc0bed33-fd93-40a6-95bb-10f27c641863/20260128T100000/ 14:46:35 present+ 15:00:28 present+ plh 15:01:04 just a sec 15:01:22 present+ mustaq 15:01:43 present+ vmpstr 15:01:52 present+ smaug 15:03:04 TOPIC: Recharter https://github.com/w3c/strategy/issues/515 15:03:35 Patrick: outstanding on which types of gestures. 15:03:50 s/outstanding/outstanding document/ 15:03:54 flackr has joined #pointerevents 15:03:58 present+ 15:03:58 ... that's WIP on my part 15:04:14 Patrick: filed this a few minutes ago https://github.com/w3c/pointerevents/issues/636 15:06:12 Patrick: looking at at the various available events and refining them 15:06:31 ... mostly Apple and Hanner.js 15:06:40 s/Hanner/Hammer/ 15:07:07 ... taking ideas from both 15:07:38 ... pan is probably not needed 15:08:23 flackr: we could eventually add more events, like skills. not necessary for our first iteration 15:09:08 plh: might be good to come up with user requirements/technical requirements to focus our effort / give us a plan 15:09:55 patrick: we talked about swipe, rotation, and zoom 15:10:28 ... we would start with swipe (multiple pointers or not?) 15:11:05 ... an other idea: things to do with coalesced events, ie adding references to them 15:11:21 ... ie finding the event streams for each individual gesture 15:11:50 flackr: coalesced would give a list of gesture, and you can dig further 15:12:18 ... mostly take the apple thing and improving will be very amenable to them 15:12:53 Patrick: you mentioned swipe could be detected with those 2 15:13:33 mustaq: from dev prospective, [...] 15:14:06 flackr: hammer swipe one fires continuously ? 15:14:14 patrick: I think it fires at the end 15:14:53 ... dev just want to know if the user swiped left 15:15:14 flackr: they'll need feedback, ie the user is swiping. so some panning, then swipe 15:16:49 [from higher events to the underlying ones: swipe, pan, [...], click] 15:17:09 Patrick_H_Lauke: you could do that today... 15:17:19 flackr: pinch, zoom, rotate are difficult 15:17:25 Patrick_H_Lauke: yes, 2 or more fingers 15:17:44 mustaq: higher level events are more dev friendly 15:18:06 Patrick_H_Lauke: don't know if there is a react module for this 15:18:23 One data point for us could be: how popular the hammer.js model is. 15:19:31 plh: we should also look at other platforms (android, ios, etc.) 15:19:50 flackr: chrome was built on android events 15:20:10 Scribe: plh 15:20:17 ScribeNick: plh 15:22:08 flackr: having single event may be easier, rather than different events for different types/discrete events 15:22:53 Patrick_H_Lauke: depends on use cases, dev will want different level of events 15:23:57 philippe: we need use cases and requirements 15:27:43 plh: there is a w3c breakout day end of march. we could organise a breakout to get feedback / get requirements 15:29:14 https://github.com/w3c/breakouts-day-2026 15:30:11 deadline for proposals is 10 March 15:32:14 My quick read of Android doc suggests their model sits between Apple's and Hammer.js's: onScaleBegin...onScale...onScaleEnd 15:32:16 https://developer.android.com/reference/android/view/ScaleGestureDetector.OnScaleGestureListener 15:35:43 ACTION: patrick to create an issue in PE repo about breakout session. group to start thinking about use cases, approaches, etc 15:36:04 TOPIC: Follow-up from UI Events meeting https://docs.google.com/document/d/1iRFgqtReyomoCwZFEdRUdoW1ManD5t656CVUGJm7Xos/ 15:37:12 plh: not done addressing all feedback from 2 weeks ago, but working through. DOMActivate there's now issue in HTML specification. need to still add warnings in sections. 15:37:32 plh: talked to francois about all the dependencies 15:38:02 plh: short story, not done, should be done in 2 weeks / will try, so potentially before next UI events call we have things ready to merge after that 15:39:09 plh: will have to have a separate deeper discussion about default action. only pointing to the definition for now, but will want to tackle it more fundamentally 15:39:44 TOPIC: WPTs 15:40:06 https://w3c.github.io/pointereventswg/implementation-reports/wpt-pointerevents-2026-01-25.html 15:40:15 plh: i generated the wpt report for what i think is the relevant list of tests for v3 15:41:05 plh: plenty of fails, but overall seems "ok" 15:41:23 plh: cases where we don't have 2 implementations, but mostly seems down to bugs rather than anything else 15:43:04 plh: if group is ok with it, i'd like to ask for PE v3 to go through. deprecate v2 and tell people to use v3. then we can forget about v3 15:43:34 plh: we happy to say the results are good enough? or we want to wait? 15:43:51 olli: worth mentioning as well that some fails MAY be down to test harness 15:44:13 plh: would be good to identify which ones. i think the one related to keys (alt/control/meta/shift). lot of failures there 15:45:36 plh: lot of missing test results, i'm guessing it's down to harness 15:45:59 plh: all of the offset-x / offset-y, guess it's because we don't use them in pointer events 15:46:20 plh: in any case, i believe this is good enough. 15:47:02 plh: do you want more time to look at the results, to see if you want to improve them? 15:48:10 plh: we don't need perfection, just demonstrating there's nothing wrong with the spec 15:48:28 mustaq: will take a look at some more failures... 15:48:45 plh: up to the group to decide 15:49:38 olli: realistically, we're probably not going to fundamentally fix many more in the next 2 weeks or so. also, next interop coming up, so we could change them further 15:49:55 mustaq: we can say we'll cover some of these in interop 2026 15:50:36 Patrick: let's give it another 2 weeks, then at next meeting have a go/no go decision 15:50:48 Ok, in Firefox many of the pen tests are ""Error: action_sequence() is not implemented by testdriver-vendor.js"" 15:50:54 plh: and i can easily regenerate report, automatically updates 15:51:22 ACTION: for next meeting, review WPT test results 15:52:22 mustaq: pointerevent_pointerrawupdate_coalesced_events_attributes.https.html?touch is also surprising 15:52:58 rrsagent, make logs world-visible 15:53:04 rrsagent, generate minutes 15:53:05 I have made the request to generate https://www.w3.org/2026/01/28-pointerevents-minutes.html Patrick_H_Lauke 15:53:21 rrsagent, bye 15:53:21 I see 2 open action items saved in https://www.w3.org/2026/01/28-pointerevents-actions.rdf : 15:53:21 ACTION: patrick to create an issue in PE repo about breakout session. group to start thinking about use cases, approaches, etc [1] 15:53:21 recorded in https://www.w3.org/2026/01/28-pointerevents-irc#T15-35-43 15:53:21 ACTION: for next meeting, review WPT test results [2] 15:53:21 recorded in https://www.w3.org/2026/01/28-pointerevents-irc#T15-51-22 15:53:22 Patrick_H_Lauke: hmm, could we use some automatic AI minuting ? WHATNOT uses that, has been working, I think, relatively well