- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 18 Dec 2024 16:56:40 +0000
- To: Pointer Events Working Group <public-pointer-events@w3.org>
Dear all, the minutes for today's meeting are at https://www.w3.org/2024/12/18-pointerevents-minutes.html and copied below: PEWG 18 December 2024 Agenda: https://www.w3.org/events/meetings/66591f6b-6694-4f90-b23d-bf8f1b9dda8a/20241218T110000/ IRC log: https://www.w3.org/2024/12/18-pointerevents-irc Attendees adettenb, mustaq, Patrick_H_Lauke, smaug Chair: Patrick H. Lauke Scribe: Patrick H. Lauke * Limit the precision of floating point event fields w3c/pointerevents#517 * Action items from previous meeting * Meta-issue: update WPT to cover Pointer Events Level 3 #445 w3c/pointerevents#445 # Limit the precision of floating point event fields w3c/pointerevents#517 w3c/pointerevents#533 Patrick: did a quick PR adding a new part to security and privacy section of the spec. If people could have a look over now to see if it makes sense Patrick: chose to add to the privacy/security bit, rather than straight after IDL, as otherwise we'd have to cross-reference [group worked on refining wording of the bullet points] Patrick: are we all happy with merging this (to the Level 3 branch)? [group approved the merge Patrick: thank you all. this is now merged in to Level 3 branch, and i'll cherry-pick it into main branch (level 4) later # Action items from previous meeting https://www.w3.org/2024/12/04-pointerevents-minutes.html#ActionSummary Patrick: first one we've now just done Patrick: then we had "Rob to reflect back discussion to the issue #516" Patrick: not sure the update/reflection there happened on w3c/pointerevents#516 ... ACTION: Rob to follow up on w3c/pointerevents#516 Patrick: next we had "Olli to follow up about #509" Olli: Masayuki added a new comment to w3c/pointerevents#509 - interesting extra case, worth investigating further Patrick: leave open for further investigation then? Olli: yes, i think this needs some more test - especially in case of cross-origin iframe Mustaq: this is particularly tricky in all cases ... down to timing ... Olli: it happens earlier, different task. it may just be possible that we just don't dispatch pointermove Mustaq: any event that comes after pointerrawupdate should be treated as a separate event... Olli: pointermove is based on pointerrawupdate though Mustaq: if we treated them as separate, would it make things different? Olli: say if you remove iframe in pointerrawupdate, i guess no pointermove would fire. except in same origin case (?) Olli: this is very much an edge case.... Mustaq: should this block v3? Olli: i don't think so Patrick: agree. this sounds VERY deep in the weeds. suggest we look at this further in Level 4 ACTION: move issue 509 to future/v4, unblocking v3 Patrick: "continue investigation on #529" Mustaq: I sent a pull request. Rob was going to review but is currently out. w3c/pointerevents#532 ACTION: review the PR for our next meeting in 2025 Patrick: last one was no immediate pressure "review #516 further, but no immediate pressure to get this in for v3" w3c/pointerevents#516 # Meta-issue: update WPT to cover Pointer Events Level 3 #445 w3c/pointerevents#445 Patrick: looking good, only one left https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+ Patrick: thank you for all the hard work this year. next meeting will be 15 Janunary 2025 (!) Patrick: I will follow up on w3c/pointerevents#517 to make sure our addition to privacy/security is deemed appropriate Summary of action items * Rob to follow up on w3c/pointerevents#516 * move issue 509 to future/v4, unblocking v3 * review the PR for our next meeting in 2025 -- Patrick H. Lauke * https://www.splintered.co.uk/ * https://github.com/patrickhlauke * https://flickr.com/photos/redux/ * https://mastodon.social/@patrick_h_lauke
Received on Wednesday, 18 December 2024 16:56:47 UTC