- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 4 Jan 2023 16:43:03 +0000
- To: public-pointer-events@w3.org
Dear all, the minutes from today's meeting are at https://www.w3.org/2023/01/04-pointerevents-minutes.html and copied below: PEWG 04 January 2023 Agenda https://www.w3.org/events/meetings/ba7fe0a1-f5c1-4fed-8dcd-0f8fdc60f8e1/20230104T110000 Attendees mustaq, plh, smaug, patrick_h_lauke Chair: Patrick H. Lauke Scribe: Patrick H. Lauke, Patrick_H_Lauke * pointerout even if the pointer doesn't move? https://github.com/w3c/pointerevents/issues/457 * Coordinates of a pointercancel event https://github.com/w3c/pointerevents/issues/463 * 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 # pointerout even if the pointer doesn't move? https://github.com/w3c/pointerevents/issues/457 mustaq: tried to make a test, but was having trouble. agree though that it's the wrong behavior Olli: it's not a spec issue though, just a WPT issue, so I guess we can close this issue here? mustaq: always difficult to test things that *shouldn't* happen [discussion on how the test could be tackled] ACTION: close this issue, but make sure there's a WPT for this scenario # Coordinates of a pointercancel event https://github.com/w3c/pointerevents/issues/463 mustaq: we had a comment from a developer that pointercancel should mirror the coords of the last known good pointermove, but as browsers can fire events async, it may not always be the case Olli: there might be "some" situations where the coords are valuable, other cases where we don't even have coords mustaq: due to the async nature (example of scrolling/swiping) it's not always clear mustaq: is 0/0 the best value to send? Olli: we haven't done anything for things like pressure either... Olli: just want to pass on pointerId, and possibly isPrimary Olli: would be good to test what webkit does Patrick: so more testing. do we need any normative language in spec? mustaq: yes we should be explicit about what the values are ACTION: make a test, see how webkit behaves, add language to spec based on findings <mustaq> FYI: I already landed a WPT, which would need to be changed if we decide to move away from current Chrome behavior. <mustaq> https://github.com/web-platform-tests/wpt/pull/37435 [brief discussion with Philippe LeHegaret about W3C and going forward] # Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445 https://github.com/w3c/pointerevents/issues?q=is%3Aclosed+label%3Aneeds-wpt+ mustaq: do you have a deadline for when we want to do this? Patrick: we don't have any pressing deadline. i'd love to get to next TPAC with us going to REC, but need to check with plh about timelines. if not, no problem. also no idea how easy/hard the wpts will be to create Olli: one problem will be the secure context issues Olli: might lead to breaking issues Olli: could do with a use counter to see when things are used in non-secure context ACTION: start looking over WPTs, particularly the secure context issue # Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356 Olli: one thing we mentioned last time was to get feedback from webkit Patrick: yes, if you know anybody on the webkit side that may be suitable to be contacted about it, feel free to do so ACTION: ongoing investigation -- 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, 4 January 2023 16:43:18 UTC