14:59:15 RRSAgent has joined #pointerevents 14:59:15 logging to https://www.w3.org/2022/10/26-pointerevents-irc 15:00:09 Meeting: PEWG 15:00:14 Chair: Patrick H. Lauke 15:00:19 Agenda: https://www.w3.org/events/meetings/0d3af70c-0054-43dc-9c15-c60c5b9c3f3c/20221026T110000 15:00:28 Scribe: Patrick H. Lauke 15:00:34 ScribeNick: Patrick_H_Lauke 15:00:39 present+ Patrick_H_Lauke 15:02:27 present+ smaug 15:02:35 present+ Mustaq 15:02:37 present+ mustaq 15:03:46 TOPIC: Order of pointerover/enter/move and corresponding mouse events is different on browsers https://github.com/w3c/pointerevents/issues/454 15:04:14 Patrick: we have two pull requests for this https://github.com/w3c/pointerevents/pull/459 15:04:21 Patrick: and https://github.com/w3c/pointerevents/pull/458 15:07:39 https://mustaqahmed.github.io/web/pe-legacy-pointer-animation/legacy-pointer-animation.html 15:08:44 https://pr-preview.s3.amazonaws.com/mustaqahmed/pointerevents/pull/458.html#tracking-the-effective-position-of-the-legacy-mouse-pointer 15:09:48 [discussion on the changes in PR 458] 15:10:13 Mustaq: after the call, i'll shorten the caption. other than that i think Patrick's changes are great, but Olli please add any more comments 15:10:34 Patrick: I'm planning to tweak the webm itself to also show the actual events being fired, but for now it's good enough 15:12:40 Mustaq: one question about adding events, how to distinguish which pointer they relate to 15:13:12 Patrick: I'd say just list the mouse events for the idealised/faked legacy mouse pointer, as that's what we care about - show how it enters/leaves the two buttons even though nothing really MOVED between them 15:13:28 Patrick: what about the other PR https://github.com/w3c/pointerevents/pull/459 15:16:57 Mustaq: I think the core note is good, but give me some time to check if the second sentence needs to be tweaked to make it even clearer 15:19:01 Patrick: wonder if this note could also use an extra para about "authors should not mix and match between pointer events and mouse events" 15:19:09 Mustaq: could make it normative? 15:19:36 Like normative "recommend against mix-and-match" 15:19:40 Patrick: as spec is aimed primarily at UA devs, not authors, i'm not sure we can MANDATE what authors do. but we can make strong recommendation 15:20:22 Patrick: i'll have a think about the extra recommendation, and mustaq feel free to comment with changes to second sentence 15:20:34 ACTION: Patrick and Mustaq to tweak PR 459 further 15:21:21 ACTION: Mustaq to make first stab at new webm showing orange mouse events being dispatched for #458 15:21:22 https://github.com/w3c/pointerevents/pull/458 : Add a note and diagram to clarify legacy mouse pointer behavior. 15:22:06 TOPIC: pointerout even if the pointer doesn't move? https://github.com/w3c/pointerevents/issues/457 15:22:18 PAtrick: there was an action ACTION: add WPT that reflects both Safari and Firefox, investigate reason for Chrome's behaviour 15:22:45 Mustaq: i might not have mentioned, but plan to address this as part of Interop 2022. please assign to me, looks like chrome bug 15:23:23 ACTION: Mustaq to review/action #457 15:23:23 https://github.com/w3c/pointerevents/issues/457 : pointerout even if the pointer doesn't move? 15:23:35 TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445 15:23:35 https://github.com/w3c/pointerevents/issues?page=1&q=is%3Aclosed+label%3Awpt 15:24:02 https://searchfox.org/mozilla-central/search?q=&path=testing%2Fweb-platform%2Ftests%2Fpointerevents&case=false®exp=false 15:24:16 Olli: maybe easiest might to search in the above url 15:24:56 Patrick: I was looking briefly over this https://github.com/web-platform-tests/wpt/tree/master/pointerevents but there's probably better 15:25:22 Mustaq: I was looking at #456 and was about to remove the wpt tag, but then realised the test we have doesn't fully cover this 15:25:23 https://github.com/w3c/pointerevents/pull/456 : Fix stale text around click, auxclick and contextmenu events 15:27:07 [discussion on how to best handle notes about whether or not WPTs are there, or if they're incomplete] 15:27:56 Patrick: so we'll note in the pull request itself whether a test exists (as part of then removing the WPT label), or add a comment of incomplete/missing tests (and leave the WPT label intact) 15:28:28 TOPIC: Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356 15:29:11 ACTION: everybody review the WPT labelled PRs and note/comment where tests are present (and remove WPT label), or if they're incomplete/missing 15:29:29 Olli: I don't think that (#356) is part of the Interop effort 15:29:29 https://github.com/w3c/pointerevents/issues/356 : Clarify what the target of the click event should be after capturing pointer events 15:29:48 Mustaq: we need to evaluate this still before proceeding 15:30:28 Patrick: looking over any other open/outstanding issues https://github.com/w3c/pointerevents/issues?q=is%3Aissue+is%3Aopen+label%3Av3 15:31:40 Mustaq: if you want to work on something on the interop list, just add your name to it... 15:31:42 https://docs.google.com/spreadsheets/d/1K3lnen0hP0T3z7lDmUnTtTrA-qWJ5JVTvkuvhV8AQhY/edit#gid=0 15:31:44 PE Interop list is here: 15:31:44 https://docs.google.com/spreadsheets/d/1K3lnen0hP0T3z7lDmUnTtTrA-qWJ5JVTvkuvhV8AQhY/edit#gid=0 15:32:20 Patrick: only other issue i can see is https://github.com/w3c/pointerevents/issues/357 15:32:46 Patrick: which we said we'll park until 356 is addressed 15:33:27 Patrick: we may need to defer #356 and #357 for future version, if they take too long to investigate/come to an agreement 15:33:28 https://github.com/w3c/pointerevents/issues/356 : Clarify what the target of the click event should be after capturing pointer events 15:33:29 https://github.com/w3c/pointerevents/issues/357 : Clarify when lostpointercapture should fire 15:36:59 Patrick: not seeing any other major issues marked as v3 otherwise, and all other issues in issue tracker are marked as future, so we're in good shape. thank you both. let's iterate over the two open PRs a bit more, and the WPT list, and meet again in two weeks' time 15:37:05 RRSAgent, set logs world-visible 15:37:09 RRSAgent, generate minutes 15:37:09 I have made the request to generate https://www.w3.org/2022/10/26-pointerevents-minutes.html Patrick_H_Lauke 15:37:14 RRSAgent, set logs world-visible 15:50:50 rrsagent, bye 15:50:50 I see 4 open action items saved in https://www.w3.org/2022/10/26-pointerevents-actions.rdf : 15:50:50 ACTION: Patrick and Mustaq to tweak PR 459 further [1] 15:50:50 recorded in https://www.w3.org/2022/10/26-pointerevents-irc#T15-20-34 15:50:50 ACTION: Mustaq to make first stab at new webm showing orange mouse events being dispatched for #458 [2] 15:50:50 recorded in https://www.w3.org/2022/10/26-pointerevents-irc#T15-21-21 15:50:50 ACTION: Mustaq to review/action #457 [3] 15:50:50 recorded in https://www.w3.org/2022/10/26-pointerevents-irc#T15-23-23 15:50:50 ACTION: everybody review the WPT labelled PRs and note/comment where tests are present (and remove WPT label), or if they're incomplete/missing [4] 15:50:50 recorded in https://www.w3.org/2022/10/26-pointerevents-irc#T15-29-11 15:50:57 https://github.com/w3c/pointerevents/pull/458 : Add a note and diagram to clarify legacy mouse pointer behavior. 15:51:01 https://github.com/w3c/pointerevents/issues/457 : pointerout even if the pointer doesn't move?