14:48:55 <RRSAgent> RRSAgent has joined #pointerevents
14:48:55 <RRSAgent> logging to https://www.w3.org/2022/07/06-pointerevents-irc
14:54:31 <Patrick_H_Lauke> Meeting: PEWG
14:54:41 <Patrick_H_Lauke> Chair: Patrick H. Lauke
14:55:06 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/0d3af70c-0054-43dc-9c15-c60c5b9c3f3c/20220706T110000
14:55:17 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
14:55:27 <Patrick_H_Lauke> ScribeNick: Patrick_H_Lauke
14:55:32 <Patrick_H_Lauke> present+ Patrick_H_Lauke
14:57:22 <Patrick_H_Lauke> regrets+ smaug
15:01:26 <flackr> flackr has joined #pointerevents
15:03:24 <Patrick_H_Lauke> present+ flackr
15:03:30 <Patrick_H_Lauke> present+ mustaq
15:04:25 <Patrick_H_Lauke> Topic: pointerrawupdate missing in "Attributes and default actions" https://github.com/w3c/pointerevents/issues/451
15:05:57 <Patrick_H_Lauke> Rob: it should be identical to pointermove
15:06:04 <Patrick_H_Lauke> Patrick: do we have concerns about bubbling?
15:06:10 <Patrick_H_Lauke> Mustaq: it shouldn't bubble
15:06:26 <Patrick_H_Lauke> Rob: we currently do fire it like pointermove, so would be a gotcha for devs if it was different from pointermove
15:06:55 <Patrick_H_Lauke> Rob: I assume that's also how all other browsers behave. if not, we can discuss it
15:07:17 <Patrick_H_Lauke> Rob: so i'd say just copy the pointermove
15:07:23 <Patrick_H_Lauke> Mustaq: but no default action
15:07:36 <mustaq> Making it bubble like poinbtermove sounds good
15:07:41 <Patrick_H_Lauke> Patrick: so bubbles yes, cancelable no, and no default action
15:07:58 <Patrick_H_Lauke> Action: add pointerrawupdate to table as per above
15:08:38 <Patrick_H_Lauke> Topic: Should we add ongotpointercapture and onlostpointercapture to the mixin extension https://github.com/w3c/pointerevents/issues/448
15:09:39 <Patrick_H_Lauke> Patrick: this is where i'm a bit hazy about what should/shouldn't go there
15:09:52 <Patrick_H_Lauke> Mustaq: global event handler predates event listener / is an older concept
15:10:47 <Patrick_H_Lauke> Mustaq: we shouldn't add new events to this global handler? that's my impression
15:12:30 <mustaq> I see Chrome has them too: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/interfaces/pointerevents.idl?q=idl$%20onpointermove
15:13:15 <Patrick_H_Lauke> Rob: aren't those two already listed?
15:13:31 <Patrick_H_Lauke> Patrick: oh...i think i got the wrong end of the stick/missed them in my haste to file an issue...
15:13:42 <mustaq> Corrected link: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/dom/global_event_handlers.idl
15:14:36 <Patrick_H_Lauke> Patrick: in @dontcallmedom's change he had https://github.com/w3c/pointerevents/commit/3fb15cc2ac8d7cfb8140d4959edb7edff8c9831b the events marked up as {{GlobalEventHandlers/pointermove}} etc ... so this is probably more about using that respec convention in the prose
15:15:24 <mustaq> I take back my comment about global event handlers.
15:16:31 <Patrick_H_Lauke> Action: Patrick to sort out https://github.com/w3c/pointerevents/issues/448 using correct respec way of referencing those two events throughout
15:16:44 <Patrick_H_Lauke> TOPIC: Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356
15:17:05 <Patrick_H_Lauke> Mustaq: started filing chrome issues, we have quite a few
15:17:21 <Patrick_H_Lauke> Mustaq: mouse has one issue of course, which we discussed here
15:17:44 <Patrick_H_Lauke> Mustaq: that one is easy. filed 4 for touch, which are harder
15:18:11 <Patrick_H_Lauke> Mustaq: once all bugs are fixed, we should check that this issue specifically is addressed
15:18:23 <Patrick_H_Lauke> Rob: would it be helpful to add link to this issue on the chrome issues?
15:18:26 <Patrick_H_Lauke> Mustaq: will do
15:18:45 <mustaq> correction: I filed 2 or touches
15:19:01 <mustaq> Mouse: https://crbug.com/1342209
15:19:18 <mustaq> Touch: https://crbug.com/1342214 and https://crbug.com/1342219
15:19:29 <Patrick_H_Lauke> Mustaq: may need one more
15:19:41 <mustaq> ...one more on explicit release.
15:19:55 <Patrick_H_Lauke> Action: carry on with those filed bugs, retest at the end
15:20:00 <Patrick_H_Lauke> Topic: Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445
15:21:55 <Patrick_H_Lauke> Rob: generally we have tests as we implement things, so we should have everything. will just be a case of checking and confirming
15:22:12 <Patrick_H_Lauke> ACTION: everybody have a look at WPT to see if there are any gaps/edge cases we need to test
15:22:33 <mustaq> https://github.com/w3c/pointerevents/issues?q=is%3Aissue+is%3Aclosed+label%3Av3+
15:24:42 <Patrick_H_Lauke> Rob: so we want that list in the issue to cover everything new added to v3, and then tick it off?
15:24:52 <Patrick_H_Lauke> Patrick: initially thought just noting what we're missing
15:25:00 <Patrick_H_Lauke> Rob: listing everthing avoids duplicate work
15:25:04 <Patrick_H_Lauke> Patrick: ok, let's go with that
15:27:54 <Patrick_H_Lauke> [some more discussion on best approach]
15:27:59 <mustaq> Exclude the editorial issues?
15:28:00 <mustaq> https://github.com/w3c/pointerevents/issues?q=is%3Aissue+is%3Aclosed+label%3Av3+-label%3Aeditorial
15:28:36 <Patrick_H_Lauke> Mustaq: we can go over the closed list of pull requests (from https://w3c.github.io/pointerevents/#revision-history) that are substantive/not editorial, add a "needs-wpt" label, and then remove the label when we confirm it has
15:29:44 <Patrick_H_Lauke> Action: Patrick to go over list of closed v3 pull requests that are substantive, add "needs-wpt" label
15:30:52 <Patrick_H_Lauke> Patrick: as a side note, for those involved in the touch events CG, if you have time/ideas on any of the open issues here (like new one from zcorpan), any thoughts appreciated https://github.com/w3c/touch-events/issues
15:32:41 <Patrick_H_Lauke> rrsagent, set logs world-visible
15:32:45 <Patrick_H_Lauke> rrsagent, generate minutes
15:32:45 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/06-pointerevents-minutes.html Patrick_H_Lauke
15:32:51 <Patrick_H_Lauke> rrsagent, set logs world-visible
15:33:14 <Patrick_H_Lauke> rrsagent, bye
15:33:14 <RRSAgent> I see 5 open action items saved in https://www.w3.org/2022/07/06-pointerevents-actions.rdf :
15:33:14 <RRSAgent> ACTION: add pointerrawupdate to table as per above [1]
15:33:14 <RRSAgent>   recorded in https://www.w3.org/2022/07/06-pointerevents-irc#T15-07-58
15:33:14 <RRSAgent> ACTION: Patrick to sort out https://github.com/w3c/pointerevents/issues/448 using correct respec way of referencing those two events throughout [2]
15:33:14 <RRSAgent>   recorded in https://www.w3.org/2022/07/06-pointerevents-irc#T15-16-31
15:33:14 <RRSAgent> ACTION: carry on with those filed bugs, retest at the end [3]
15:33:14 <RRSAgent>   recorded in https://www.w3.org/2022/07/06-pointerevents-irc#T15-19-55
15:33:14 <RRSAgent> ACTION: everybody have a look at WPT to see if there are any gaps/edge cases we need to test [4]
15:33:14 <RRSAgent>   recorded in https://www.w3.org/2022/07/06-pointerevents-irc#T15-22-12
15:33:14 <RRSAgent> ACTION: Patrick to go over list of closed v3 pull requests that are substantive, add "needs-wpt" label [5]
15:33:14 <RRSAgent>   recorded in https://www.w3.org/2022/07/06-pointerevents-irc#T15-29-44