16:01:47 <RRSAgent> RRSAgent has joined #pointerevents
16:01:51 <RRSAgent> logging to https://www.w3.org/2023/01/04-pointerevents-irc
16:02:39 <Patrick_H_Lauke> Meeting: PEWG
16:02:48 <Patrick_H_Lauke> Chair: Patrick H. Lauke
16:03:08 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/ba7fe0a1-f5c1-4fed-8dcd-0f8fdc60f8e1/20230104T110000
16:03:14 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
16:03:22 <Patrick_H_Lauke> ScribeNick: Patrick_H_Lauke
16:05:34 <mustaq> present+
16:05:40 <Patrick_H_Lauke> present+ smaug
16:05:44 <Patrick_H_Lauke> TOPIC: pointerout even if the pointer doesn't move? https://github.com/w3c/pointerevents/issues/457
16:07:51 <Patrick_H_Lauke> mustaq: tried to make a test, but was having trouble. agree though that it's the wrong behavior
16:08:56 <Patrick_H_Lauke> Olli: it's not a spec issue though, just a WPT issue, so I guess we can close this issue here?
16:11:03 <Patrick_H_Lauke> mustaq: always difficult to test things that *shouldn't* happen
16:11:17 <Patrick_H_Lauke> [discussion on how the test could be tackled]
16:13:14 <Patrick_H_Lauke> ACTION: close this issue, but make sure there's a WPT for this scenario
16:13:42 <Patrick_H_Lauke> TOPIC: Coordinates of a pointercancel event https://github.com/w3c/pointerevents/issues/463
16:15:21 <Patrick_H_Lauke> 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
16:16:17 <Patrick_H_Lauke> Olli: there might be "some" situations where the coords are valuable, other cases where we don't even have coords
16:16:44 <Patrick_H_Lauke> mustaq: due to the async nature (example of scrolling/swiping) it's not always clear
16:16:56 <Patrick_H_Lauke> mustaq: is 0/0 the best value to send?
16:17:23 <Patrick_H_Lauke> Olli: we haven't done anything for things like pressure either...
16:17:43 <Patrick_H_Lauke> Olli: just want to pass on pointerId, and possibly isPrimary
16:18:07 <Patrick_H_Lauke> present+ plh
16:21:17 <Patrick_H_Lauke> Olli: would be good to test what webkit does
16:21:35 <Patrick_H_Lauke> Patrick: so more testing. do we need any normative language in spec?
16:21:45 <Patrick_H_Lauke> mustaq: yes we should be explicit about what the values are
16:22:14 <Patrick_H_Lauke> ACTION: make a test, see how webkit behaves, add language to spec based on findings
16:24:03 <mustaq> FYI: I already landed a WPT, which would need to be changed if we decide to move away from current Chrome behavior.
16:24:36 <mustaq> https://github.com/web-platform-tests/wpt/pull/37435
16:27:04 <Patrick_H_Lauke> [brief discussion with Philippe LeHegaret about W3C and going forward]
16:27:24 <Patrick_H_Lauke> TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445
16:27:24 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/issues?q=is%3Aclosed+label%3Aneeds-wpt+
16:30:56 <Patrick_H_Lauke> mustaq: do you have a deadline for when we want to do this?
16:31:42 <Patrick_H_Lauke> 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
16:31:59 <Patrick_H_Lauke> Olli: one problem will be the secure context issues
16:32:07 <Patrick_H_Lauke> Olli: might lead to breaking issues
16:32:35 <Patrick_H_Lauke> Olli: could do with a use counter to see when things are used in non-secure context
16:33:07 <Patrick_H_Lauke> ACTION: start looking over WPTs, particularly the secure context issue
16:34:17 <Patrick_H_Lauke> TOPIC: Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356
16:35:10 <Patrick_H_Lauke> Olli: one thing we mentioned last time was to get feedback from webkit
16:35:31 <Patrick_H_Lauke> Patrick: yes, if you know anybody on the webkit side that may be suitable to be contacted about it, feel free to do so
16:35:42 <Patrick_H_Lauke> ACTION: ongoing investigation
16:39:10 <Patrick_H_Lauke> RRSAgent, make logs world-visible
16:39:15 <Patrick_H_Lauke> RRSAgent, generate minutes
16:39:16 <RRSAgent> I have made the request to generate https://www.w3.org/2023/01/04-pointerevents-minutes.html Patrick_H_Lauke
16:39:30 <Patrick_H_Lauke> RRSAgent, make logs world-visible
20:23:10 <Patrick_H_Lauke> rrsagent, bye
20:23:10 <RRSAgent> I see 4 open action items saved in https://www.w3.org/2023/01/04-pointerevents-actions.rdf :
20:23:10 <RRSAgent> ACTION: close this issue, but make sure there's a WPT for this scenario [1]
20:23:10 <RRSAgent>   recorded in https://www.w3.org/2023/01/04-pointerevents-irc#T16-13-14
20:23:10 <RRSAgent> ACTION: make a test, see how webkit behaves, add language to spec based on findings [2]
20:23:10 <RRSAgent>   recorded in https://www.w3.org/2023/01/04-pointerevents-irc#T16-22-14
20:23:10 <RRSAgent> ACTION: start looking over WPTs, particularly the secure context issue [3]
20:23:10 <RRSAgent>   recorded in https://www.w3.org/2023/01/04-pointerevents-irc#T16-33-07
20:23:10 <RRSAgent> ACTION: ongoing investigation [4]
20:23:10 <RRSAgent>   recorded in https://www.w3.org/2023/01/04-pointerevents-irc#T16-35-42