15:53:47 RRSAgent has joined #pointerevents 15:53:47 logging to https://www.w3.org/2022/11/23-pointerevents-irc 15:53:59 Meeting: PEWG 15:54:02 Chair: Patrick H. Lauke 15:54:08 Agenda: https://www.w3.org/events/meetings/0d3af70c-0054-43dc-9c15-c60c5b9c3f3c/20221123T110000 15:54:16 Scribe: Patrick H. Lauke 15:54:22 ScribeNick: Patrick_H_Lauke 15:54:30 present+ Patrick_H_Lauke 15:58:11 present+ smaug 16:01:08 flackr has joined #pointerevents 16:02:31 present+ flackr 16:02:36 present+ mustaq 16:03:39 TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445 16:03:39 https://github.com/w3c/pointerevents/issues?page=1&q=is%3Aclosed+label%3Awpt 16:04:42 Olli: I've added "needs-wpt" to PRs that I looked at and that then need a test https://github.com/w3c/pointerevents/issues?q=is%3Aclosed+label%3Aneeds-wpt+ 16:05:15 And we already have 6 PRs marked as "needs-wpt" 16:05:46 Patrick: so if you find any that have just the "wpt" tag and are sure that it's not something we need/can have a test for, just remove the tag 16:06:02 Patrick: so in the end we'll hopefully be left just with "needs-wpt" ones and none with "wpt" 16:06:46 Olli: I did have a question about coalesced events etc in secure context - seems no browser does it, and WPT runs tests just as http. 16:06:58 Mustaq: do you have an issue for that? 16:07:09 https://wpt.fyi/results/pointerevents/idlharness.window.html?label=master&label=experimental&aligned&view=subtest&q=idlharness 16:07:44 Olli: if you run this in your browser for wpt live, it's using a NON-secure context as it's just http not https 16:09:14 Olli: if you manually add https, you can run the test in secure context. but yes, running the test even in http passes in firefox at least 16:09:23 Olli: when it should only pass in secure context 16:10:41 ACTION: carry on working through remaining "wpt" PRs until we have none left and only "needs-wpt" left, then we can divide workload on how to get tests done 16:11:21 Mustaq: [asking about which PR the secure context relates to] 16:11:24 Patrick: https://github.com/w3c/pointerevents/pull/318 16:11:48 Olli: test might just need to test the window/securecontext flag 16:12:09 TOPIC: Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356 16:13:24 [no movement on this one yet] 16:13:40 Patrick: we may have to see if we can somehow defer this for next version, as otherwise this may hold up spec indefinitely 16:14:15 TOPIC: new pull request about popover light dismiss integration https://github.com/w3c/pointerevents/pull/460 16:15:38 Patrick: I'm loathe to add anything to our spec until this is stable 16:15:57 Olli: yes, we should wait (the naming of the attribute has been in flux) 16:16:37 Rob: yes i've been involved in the discussions. it's being reviewed, but certainly not being shipped yet 16:17:00 Patrick: i'll mark as for next spec version, we can always review if this makes into into live spec before we go final 16:18:27 Patrick: unless there's other business, let's keep it short and sweet today 16:18:40 Olli: I'll carry on going through some more of the WPT pull requests 16:19:17 Patrick: thank you. I'll refresh my mind about W3C process to see what next steps are since we're now edging closer to completion. See you again in 2 weeks' time 16:19:33 RRSAgent, set logs world-visible 16:19:41 RRSAgent, create minutes 16:19:41 I have made the request to generate https://www.w3.org/2022/11/23-pointerevents-minutes.html Patrick_H_Lauke 16:19:48 RRSAgent, set logs world-visible 16:20:05 RRSAgent, bye 16:20:05 I see 1 open action item saved in https://www.w3.org/2022/11/23-pointerevents-actions.rdf : 16:20:05 ACTION: carry on working through remaining "wpt" PRs until we have none left and only "needs-wpt" left, then we can divide workload on how to get tests done [1] 16:20:05 recorded in https://www.w3.org/2022/11/23-pointerevents-irc#T16-10-41