14:57:37 <RRSAgent> RRSAgent has joined #pointerevents
14:57:41 <RRSAgent> logging to https://www.w3.org/2023/03/29-pointerevents-irc
14:57:46 <Patrick_H_Lauke> Meeting: PEWG
14:57:49 <Patrick_H_Lauke> Chair: Patrick H. Lauke
14:57:53 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/81ad3e7c-6dde-48ec-8693-09a9adea9f69/20230329T110000
14:58:01 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
14:58:08 <Patrick_H_Lauke> ScribeNick: Patrick_H_Lauke
14:58:10 <Patrick_H_Lauke> present+
15:00:31 <smaug> preset+
15:01:02 <smaug> present+
15:01:04 <flackr> flackr has joined #pointerevents
15:02:09 <Patrick_H_Lauke> present+ smaug
15:02:18 <Patrick_H_Lauke> present+ flackr
15:06:13 <Patrick_H_Lauke> TOPIC: TPAC 2023
15:10:09 <Patrick_H_Lauke> Patrick: just checking if you are attending TPAC this year?
15:10:21 <Patrick_H_Lauke> [Olli and Rob say yes]
15:11:00 <Patrick_H_Lauke> Patrick: I might be physically there as well this year. So we ok to say tentatively that we'll go for a short 90 minute session?
15:11:02 <Patrick_H_Lauke> [Group agrees]
15:11:31 <Patrick_H_Lauke> Patrick: we might even be at the stage then when most of our work on v3 is done and we just do a live meeting to agree to push the button to go for publication etc
15:11:49 <Patrick_H_Lauke> Rob: maybe Intel will want to re-present their session from last time
15:12:10 <Patrick_H_Lauke> Patrick: ah yes, you weren't there. They might yes, or they may present separately/independently from us
15:12:21 <Patrick_H_Lauke> [Group does a quick recap of what was presented]
15:12:50 <Patrick_H_Lauke> ACTION: Patrick to check what is required in terms of requesting/scheduling session at TPAC
15:13:05 <Patrick_H_Lauke> TOPIC: Investigate if tangentialPressure is correctly implemented/working in browsers/documented appropriately in spec
15:13:05 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/issues/467
15:15:18 <mustaq> present+
15:17:37 <mustaq> (I plan to join TPAC too)
15:19:27 <Patrick_H_Lauke> Patrick: since the last meeting, I looked at implementations and filed bugs against Chrome and Firefox. but the spec *is* correct, despite the weird naming (which I believe came from HID originally). I do plan on adding an extra non-normative note to explain that despite the name "tangentialPressure" it may or may not actually have anything to do with pressure. and that it doesn't interact with the "pressure" value. Wacom[CUT]
15:19:27 <Patrick_H_Lauke> stic tool calls it "Wheel"
15:19:38 <Patrick_H_Lauke> Rob: is there any scope for us renaming tangentialPressure?
15:19:51 <Patrick_H_Lauke> Patrick: doubt it, it's been there since v1, and the name does come from I believe the HID
15:20:03 <Patrick_H_Lauke> Olli: there's only support on macOS, so maybe we can...
15:23:56 <smaug> https://het.as.utexas.edu/HET/Software/html/qtabletevent.html#tangentialPressure
15:24:16 <Patrick_H_Lauke> https://developer.apple.com/documentation/appkit/nsevent/1525959-tangentialpressure
15:27:56 <Patrick_H_Lauke> ACTION: Patrick to write small additional note, we're not going to rename the property due to prior art/other places that use the term, as unfortunate as it is, then close the issue
15:28:26 <Patrick_H_Lauke> TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues/445
15:28:26 <Patrick_H_Lauke> Go over https://github.com/w3c/pointerevents/issues?q=is%3Aclosed+label%3Aneeds-wpt+
15:29:09 <Patrick_H_Lauke> Mustaq: I have a few more in a local patch, slowly working on this
15:29:43 <Patrick_H_Lauke> Patrick: if anybody needs help, shout (if they can help me set up local env etc)
15:29:49 <Patrick_H_Lauke> Olli: yes I need to fix some of mine
15:30:04 <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
15:30:14 <Patrick_H_Lauke> Patrick: as ever, don't think we've had much progress on this
15:31:28 <Patrick_H_Lauke> Patrick: we probably need to start planning what we do with this...whether we add a note to spec, quietly ignore it...
15:31:50 <Patrick_H_Lauke> Mustaq: there's always a risk changing code in Chrome
15:32:16 <Patrick_H_Lauke> Olli: same for Firefox
15:32:45 <Patrick_H_Lauke> Patrick: maybe for next meeting we should re-familiarise ourselves with this, and make a commitment that we'll make some decision on this either way
15:33:25 <Patrick_H_Lauke> [some more discussion to re-familiarise ourselves]
15:34:17 <Patrick_H_Lauke> Rob: I'd be interested about what Safari (Mobile) does here. we should add that to ticket. mouse is the easy scenario, we need to look at touch and harmonise on that
15:34:48 <Patrick_H_Lauke> Mustaq: if we could test on mobile for touch and add those results to the table, that would help
15:35:09 <Patrick_H_Lauke> ACTION: Patrick to test and document #356 on touch
15:35:10 <Github> https://github.com/w3c/pointerevents/issues/356 : Clarify what the target of the click event should be after capturing pointer events
15:36:20 <Patrick_H_Lauke> Mustaq: I think in principle we're agreed it's the right thing to do, but need to run a trial to help decide
15:37:46 <Patrick_H_Lauke> Patrick: pre-warning you that I'm on holiday in 2 weeks' time, so next meeting will be in 4 weeks. Thank you all
15:37:56 <Patrick_H_Lauke> rrsagent, make minutes world-visible
15:37:56 <RRSAgent> I'm logging. I don't understand 'make minutes world-visible', Patrick_H_Lauke.  Try /msg RRSAgent help
15:38:18 <Patrick_H_Lauke> rrsagent, set logs world-visible
15:38:24 <Patrick_H_Lauke> rrsagent, generate minutes
15:38:25 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/29-pointerevents-minutes.html Patrick_H_Lauke
15:38:46 <Patrick_H_Lauke> rrsagent, bye
15:38:46 <RRSAgent> I see 3 open action items saved in https://www.w3.org/2023/03/29-pointerevents-actions.rdf :
15:38:46 <RRSAgent> ACTION: Patrick to check what is required in terms of requesting/scheduling session at TPAC [1]
15:38:46 <RRSAgent>   recorded in https://www.w3.org/2023/03/29-pointerevents-irc#T15-12-50
15:38:46 <RRSAgent> ACTION: Patrick to write small additional note, we're not going to rename the property due to prior art/other places that use the term, as unfortunate as it is, then close the issue [2]
15:38:46 <RRSAgent>   recorded in https://www.w3.org/2023/03/29-pointerevents-irc#T15-27-56
15:38:46 <RRSAgent> ACTION: Patrick to test and document #356 on touch [3]
15:38:46 <RRSAgent>   recorded in https://www.w3.org/2023/03/29-pointerevents-irc#T15-35-09
15:39:00 <Github> https://github.com/w3c/pointerevents/issues/356 : Clarify what the target of the click event should be after capturing pointer events