15:06:34 <RRSAgent> RRSAgent has joined #pointerevents
15:06:38 <RRSAgent> logging to https://www.w3.org/2023/09/14-pointerevents-irc
15:06:40 <Zakim> Zakim has joined #pointerevents
15:06:54 <plh> rrsagent, make minute s public
15:06:54 <RRSAgent> I'm logging. I don't understand 'make minute s public', plh.  Try /msg RRSAgent help
15:07:04 <plh> rrsagent, make minutes public
15:07:04 <RRSAgent> I'm logging. I don't understand 'make minutes public', plh.  Try /msg RRSAgent help
15:07:04 <Patrick_H_Lauke> Meeting: PEWG
15:07:23 <Patrick_H_Lauke> Chair: Patrick H. Lauke
15:07:32 <Patrick_H_Lauke> ChairNick: Patrick_H_Lauke
15:07:35 <Patrick_H_Lauke> present+
15:07:40 <Patrick_H_Lauke> present+ smaug
15:07:43 <Patrick_H_Lauke> present+ flackr
15:08:17 <Patrick_H_Lauke> present+ mustaq
15:08:17 <Patrick_H_Lauke> present+ plh
15:08:17 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/b7eb56a3-7c45-4aaa-acaf-de56a32919f2/
15:08:29 <Patrick_H_Lauke> TOPIC: Presentation/demos submitted to https://www.w3.org/2023/09/TPAC/demos/pointer-events.html
15:11:02 <Patrick_H_Lauke> Patrick: was good experience to put the slides/demos together, to rationalise some use cases myself
15:12:06 <Patrick_H_Lauke> Patrick: had interesting discussion with somebody on mastodon about "if we have getCoalescedEvents(), why do we need pointerrawupadte?@
15:12:06 <Patrick_H_Lauke> Patrick: and that made me think of situations where you MAY want to react to things quickly. but for drawing applications they're probably both solving the same situation. May be worth putting a note in the spec explaining some use cases
15:12:48 <smaug> https://github.com/WICG/scheduling-apis/issues/67
15:12:49 <Patrick_H_Lauke> Olli: don't know if you've seen this scheduling issue. can you comment on the issue where pointerrawupdate is handled in Blink?
15:12:58 <Patrick_H_Lauke> TOPIC: Review outstanding v3-blocker issues https://github.com/w3c/pointerevents/issues?q=is%3Aissue+is%3Aopen+label%3Av3-blocking
15:13:40 <Patrick_H_Lauke> TOPIC: Clarify pointerleave and pointerout events when first pointer move after removing an element under the pointer https://github.com/w3c/pointerevents/issues/477
15:14:33 <Patrick_H_Lauke> mustaq: I think we can close this one. made a suggestion for interop/wpt
15:14:57 <Patrick_H_Lauke> Rob: path forward on this. we've updated the WPT, submitted a patch in chrome
15:15:12 <Patrick_H_Lauke> Rob: this requires changes in Firefox and Safari as well
15:15:46 <Patrick_H_Lauke> Rob: Firefox, when node is removed, it's like you're over no node anymore. this is a change from that behaviour
15:16:20 <Patrick_H_Lauke> Rob: chrome used to match previous (?) Safari behaviour where it was trying to remember the previous node
15:16:39 <Patrick_H_Lauke> Rob: we don't have interop right now, but planned fix will match developer expectation
15:17:12 <Patrick_H_Lauke> Patrick: do we close this issue? or do we wait until we do have interop?
15:17:45 <Patrick_H_Lauke> Olli: what happens with shadow DOM, where you remove the content of a slot and it falls back to default slot content
15:18:08 <Patrick_H_Lauke> Rob: the implicit node is the parent, but on the next movement you're in the new default content that is shown
15:19:44 <Patrick_H_Lauke> Olli: mouse is over slotted element, remove that...store the parent. then it goes to the slot, but that doesn't have a box, but then it gets content on next paint...
15:20:02 <Patrick_H_Lauke> Rob: ... on the next move you need to fire the event on the default content that went back into the slot
15:22:36 <mustaq> Chrome work in progress, we expect to send out an intent to ship in a few weeks.
15:22:53 <Patrick_H_Lauke> TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 https://github.com/w3c/pointerevents/issues?q=is%3Aclosed+label%3Aneeds-wpt+
15:23:22 <Patrick_H_Lauke> Patrick: still have 5 issues open
15:24:00 <Patrick_H_Lauke> Mustaq: I started work on #411
15:24:48 <Patrick_H_Lauke> Olli: worked on #390 - will need manual testing
15:25:22 <Patrick_H_Lauke> Patrick: any blockers/problems/ideas/suggestions for any other ones that are still open
15:25:24 <Patrick_H_Lauke> ?
15:26:54 <Patrick_H_Lauke> Mustaq: #474, do we still leave the issue open here as well?
15:27:24 <Patrick_H_Lauke> Rob: it should be possible to do a test? we don't have a test yet?
15:27:39 <Patrick_H_Lauke> Rob: we could at least get it tested. no browser is currently implementing it correctly...
15:28:55 <Patrick_H_Lauke> Patrick: what about #318?
15:29:10 <Patrick_H_Lauke> Olli: this was discussed last time, we should have test soon
15:29:32 <Patrick_H_Lauke> Patrick: last one is #300 ...
15:30:10 <Patrick_H_Lauke> Olli: this should also be easy to test. I think Firefox may not pass this ... or maybe it does?
15:31:12 <Patrick_H_Lauke> TOPIC: Next steps for the spec
15:31:40 <Patrick_H_Lauke> Plh: I opened an issue - wide review for pointer events. It's autopublishing (latest version is august 31st)
15:32:25 <Patrick_H_Lauke> Plh: we need to notify all groups and horizontal reviews. Horizontal reviews need to do issues in 5 different repositories, but these are all listed in that issue
15:32:46 <Patrick_H_Lauke> Plh: we will not receive review from security, because it's broken. it will time out
15:33:15 <Patrick_H_Lauke> Plh: ... who knows what we get with privacy, and what we get for accessibility/APA
15:33:25 <Patrick_H_Lauke> Plh: we're probably looking at a month or two for that
15:33:56 <Patrick_H_Lauke> Plh: another subject: charter. i started the call for you two weeks ago
15:35:27 <Patrick_H_Lauke> Plh: question if we wanted to go for living standard after v3 or not
15:35:51 <Patrick_H_Lauke> Patrick: I seem to remember we discussed this ages ago, and the conclusion was that it didn't matter either way in that we can always decide to go for it, or not
15:36:04 <Patrick_H_Lauke> Plh: correct. just wondering if we forgot about this when submitting charter renewal
15:36:16 <Patrick_H_Lauke> Patrick: fairly sure we discussed this and said "whatever is easiest"
15:36:35 <Patrick_H_Lauke> Plh: would be good to find minutes where we did say this, and link from the issue just so we can find that decision again
15:36:52 <Patrick_H_Lauke> ACTION: Patrick to review past minutes to find the ones where we decided about living standard yes or no
15:38:18 <Patrick_H_Lauke> Plh: actually, found the minutes, and seems we leant towards going for living standard. So our charter extension does not quite reflect that, but we can fix it later
15:39:49 <Patrick_H_Lauke> Patrick: so from discussions with PLH we can already ask for wide review before WPTs are all done. are we all happy with this?
15:40:01 <Patrick_H_Lauke> Patrick: anybody against the idea?
15:40:07 <Patrick_H_Lauke> Patrick: [no objections]
15:40:15 <mustaq> LGTM
15:41:45 <Patrick_H_Lauke> TOPIC: update to editors/former editors
15:42:47 <Patrick_H_Lauke> Rob: wondering about whether this should be updated, as it still shows Navid as co-editor but he has not been involved over the last year(s)?
15:43:35 <Patrick_H_Lauke> Patrick: I think when I first floated this, Navid was concerned/wanted to remain visible since coalesced events were his big contribution (if i remember correctly). I'm easy either way. Should we move him to former editors?
15:43:43 <Patrick_H_Lauke> Patrick: [group agrees]
15:43:52 <Patrick_H_Lauke> ACTION: update editors/former editors
15:45:07 <Patrick_H_Lauke> rssagent, set logs world-visible
15:45:13 <Patrick_H_Lauke> rrsagent, generate minutes
15:45:14 <RRSAgent> I have made the request to generate https://www.w3.org/2023/09/14-pointerevents-minutes.html Patrick_H_Lauke
16:03:55 <Patrick_H_Lauke> Patrick_H_Lauke has joined #pointerevents
16:11:33 <Patrick_H_Lauke> Patrick_H_Lauke has joined #pointerevents
16:22:37 <Patrick_H_Lauke> Patrick_H_Lauke has joined #pointerevents
16:23:12 <Patrick_H_Lauke> Patrick_H_Lauke has joined #pointerevents
16:48:27 <Patrick_H_Lauke> Patrick_H_Lauke has joined #pointerevents
17:00:06 <Patrick_H_Lauke> Patrick_H_Lauke has joined #pointerevents
17:40:17 <Zakim> Zakim has left #pointerevents
18:17:00 <Patrick_H_Lauke> Patrick_H_Lauke has joined #pointerevents
19:19:20 <Patrick_H_Lauke> Patrick_H_Lauke has joined #pointerevents