15:59:35 RRSAgent has joined #pointerevents 15:59:39 logging to https://www.w3.org/2024/12/04-pointerevents-irc 15:59:40 Meeting: PEWG 16:00:14 Agenda: https://www.w3.org/events/meetings/66591f6b-6694-4f90-b23d-bf8f1b9dda8a/20241204T110000/ 16:00:19 Chair: Patrick H. Lauke 16:00:23 Scribe: Patrick H. Lauke 16:00:30 ScribeNick: Patrick_H_Lauke 16:00:36 present+ 16:00:52 just a sec 16:01:02 present+ 16:01:09 present+ flackr 16:01:49 present+ smaug 16:02:25 TOPIC: Limit the precision of floating point event fields https://github.com/w3c/pointerevents/issues/517 16:03:50 Patrick: Although I promised I'd do this for today, time ran away with me. I will work on this today after the call 16:04:19 Rob: I commented on this before last meeting, pointing to animation spec that has similar wording as inspiration. Happy to review this when you have something 16:04:30 ACTION: Patrick to actually do #517 16:04:41 TOPIC: [touch actions] handwriting manipulation type to distinguish panning https://github.com/w3c/pointerevents/issues/516 16:05:58 present+ adettenb 16:06:31 Rob: considering at the moment to decouple handwriting from panning 16:06:46 adettenb: yes, panning is the scrolling action, handwriting is handwriting action 16:06:58 Rob: and if you have BOTH allowed, it's up to the UA to decide which action to do 16:07:21 Rob: that to me seems right way forward. and you have the patch going forward to address existing sites 16:08:01 Rob: if that all sounds reasonable, think to proceed we can wait for more data before going ahead 16:08:52 Mustaq: wondering where discussion is taking place... 16:09:06 Rob: some of it might be internal/chrome issue 16:09:21 Rob: however yes, would be good to reflect that back into this issue. I can make a comment 16:09:36 ACTION: Rob to reflect back discussion to the issue #516 16:09:50 TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 #445 https://github.com/w3c/pointerevents/issues/445 16:10:19 Mustaq: iframe capturing issue that Rob landed, I re-landed, so we should be good on that 16:10:32 Rob: so we can remove label/close issue 16:11:00 Patrick: https://github.com/w3c/pointerevents/issues?q=label%3Aneeds-wpt+ 16:11:09 Only remaining: https://github.com/w3c/pointerevents/issues/509 16:11:28 Olli: this was added two weeks ago 16:12:27 Olli: let me ask Masayuki if he's working on it. not v3-blocking. think spec is clear, could just do with a test 16:12:40 ACTION: Olli to follow up about #509 16:13:40 TOPIC: Unlabelled issues https://github.com/w3c/pointerevents/issues?q=is%3Aissue+is%3Aopen+-label%3Afuture+-label%3Av3++-label%3Av3-blocking 16:14:01 Mustaq: I added to this last week, sorry 16:14:23 Mustaq: #529 is about mouse, what events to fire https://github.com/w3c/pointerevents/issues/529 16:15:15 Mustaq: only remaining question is whether to fire mousemove (?) 16:15:42 Rob: UI events says that we do need to care about things mutating behind cursor. technically for mouse events, but we should follow suit for pointer events 16:15:56 Olli: but PE says only fire when pointer moves... 16:16:37 Rob: UI events used to as well, going back to 2012... used to be the case (in Chrome), we didn't always fire events when content underneath cursor changed. we should follow suit 16:16:42 Mustaq: otherwise would be confusing 16:17:00 Rob: for scrolling it happens after delay (bit handwavy). maybe we can do similar for this case. but should be consistent 16:17:17 Olli: browsers are very inconsistent at this stage. don't like the behaviour, but can live with it. 16:17:34 Olli: if you move, you get pointermove. that's that. but can live with it... 16:17:51 Rob: don't think we should fire move. but for hover states, it should be consistent 16:18:07 Mustaq: so just tying move to the physical movement 16:19:13 Patrick: just as aside, not just physical movement of mouse/finger. also fires in case of change of pressure, angle/tilt, etc 16:19:41 Olli: for boundary events, it currently talks about pointing device being moved 16:19:48 Olli: we would need some tweak there 16:22:05 Patrick: so do we have an action? 16:22:28 Mustaq: we want to match boundary events behavior, but not fire move 16:22:39 Olli: concerned about a resulting change for interop tests 16:23:15 Mustaq: will post summary comment to the issue #529 16:25:03 Mustaq: will look into a PR. how urgent is this? 16:25:18 Patrick: it might be v3-blocking, but not sure if we can realistically fix this soon? 16:26:23 Patrick: might need more time. maybe not v3-blocking ? can also just wait until v4? 16:27:03 Olli: it would be a breaking change... 16:27:07 Patrick: let's defer to v4 16:27:18 Ok I will self assign it to me. 16:27:22 ACTION: continue investigation on #529 16:27:40 Patrick: https://github.com/w3c/pointerevents/issues/530 16:27:59 Mustaq: in my opinion not v3 blocking 16:28:13 Patrick: happy to mark as future 16:29:10 Mustaq: [reads out inconsistencies he found with chorded button presses] 16:29:53 Rob: i'm inclined to think Firefox's behaviour makes sense, firing an event for each button. might not be critical for web, but for gaming 16:31:22 ACTION: review #516 further, but no immediate pressure to get this in for v3 16:31:53 Patrick: thank you all as ever. finishing early as this covers all we had at this point. catch you all again in 2 weeks' time 16:32:00 rrsagent, make logs world-visible 16:32:07 rrsagent, generate minutes 16:32:08 I have made the request to generate https://www.w3.org/2024/12/04-pointerevents-minutes.html Patrick_H_Lauke 16:32:53 rrsagent, bye 16:32:53 I see 5 open action items saved in https://www.w3.org/2024/12/04-pointerevents-actions.rdf : 16:32:53 ACTION: Patrick to actually do #517 [1] 16:32:53 recorded in https://www.w3.org/2024/12/04-pointerevents-irc#T16-04-30 16:32:53 ACTION: Rob to reflect back discussion to the issue #516 [2] 16:32:53 recorded in https://www.w3.org/2024/12/04-pointerevents-irc#T16-09-36 16:32:53 ACTION: Olli to follow up about #509 [3] 16:32:53 recorded in https://www.w3.org/2024/12/04-pointerevents-irc#T16-12-40 16:32:53 ACTION: continue investigation on #529 [4] 16:32:53 recorded in https://www.w3.org/2024/12/04-pointerevents-irc#T16-27-22 16:32:53 ACTION: review #516 further, but no immediate pressure to get this in for v3 [5] 16:32:53 recorded in https://www.w3.org/2024/12/04-pointerevents-irc#T16-31-22