- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 23 Nov 2022 16:23:39 +0000
- To: Pointer Events Working Group <public-pointer-events@w3.org>
Dear all, the minutes from today's meeting are at https://www.w3.org/2022/11/23-pointerevents-minutes.html and copied below: PEWG 23 November 2022 Agenda: https://www.w3.org/events/meetings/0d3af70c-0054-43dc-9c15-c60c5b9c3f3c/20221123T110000 Attendees: flackr, mustaq, Patrick_H_Lauke, smaug Chair: Patrick H. Lauke Scribe: Patrick H. Lauke, Patrick_H_Lauke * Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445 * Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356 * new pull request about popover light dismiss integration https://github.com/w3c/pointerevents/pull/460 # Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445 https://github.com/w3c/pointerevents/issues?page=1&q=is%3Aclosed+label%3Awpt 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+ <mustaq> And we already have 6 PRs marked as "needs-wpt" 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 Patrick: so in the end we'll hopefully be left just with "needs-wpt" ones and none with "wpt" 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. Mustaq: do you have an issue for that? <smaug> https://wpt.fyi/results/pointerevents/idlharness.window.html?label=master&label=experimental&aligned&view=subtest&q=idlharness 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 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 Olli: when it should only pass in secure context 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 Mustaq: [asking about which PR the secure context relates to] Patrick: https://github.com/w3c/pointerevents/pull/318 Olli: test might just need to test the window/securecontext flag # Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356 [no movement on this one yet] Patrick: we may have to see if we can somehow defer this for next version, as otherwise this may hold up spec indefinitely # new pull request about popover light dismiss integration https://github.com/w3c/pointerevents/pull/460 Patrick: I'm loathe to add anything to our spec until this is stable Olli: yes, we should wait (the naming of the attribute has been in flux) Rob: yes i've been involved in the discussions. it's being reviewed, but certainly not being shipped yet Patrick: i'll mark as for next spec version, we can always review if this makes into into live spec before we go final Patrick: unless there's other business, let's keep it short and sweet today Olli: I'll carry on going through some more of the WPT pull requests 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 -- Patrick H. Lauke https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Wednesday, 23 November 2022 16:23:54 UTC