14:50:26 <RRSAgent> RRSAgent has joined #pointerevents
14:50:30 <RRSAgent> logging to https://www.w3.org/2024/07/17-pointerevents-irc
14:50:30 <Patrick_H_Lauke> Meeting: PEWG
14:50:40 <Patrick_H_Lauke> Chair: Patrick H. Lauke
14:50:49 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
14:50:54 <Patrick_H_Lauke> ScribeNick: Patrick_H_Lauke
14:51:22 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/16b7312b-55ac-4645-8312-0d8103f75519/20240717T110000/
14:52:08 <Patrick_H_Lauke> present+
15:01:06 <Patrick_H_Lauke> present+ smaug
15:01:11 <Patrick_H_Lauke> present+ flackr
15:01:46 <Patrick_H_Lauke> present+ mustaq
15:01:57 <Patrick_H_Lauke> TOPIC: ‘Logical’ values for the ‘touch-action’ property https://github.com/w3c/pointerevents/issues/505
15:02:34 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/pull/496
15:09:38 <Patrick_H_Lauke> [group discusses the proposed touch-action values, and whether or not they make sense - i.e. does pan-inline-start mean moving towards, or away from, the inline-start. same issue arguably with left/right/etc. group agreed it *may* be clear enough as is]
15:10:16 <Patrick_H_Lauke> mustaq: what happens if writing mode/direction changes in a child, and you start panning on that. does it affect it?
15:10:31 <Patrick_H_Lauke> [further explanation/discussion]
15:10:56 <Patrick_H_Lauke> Rob: it should be irrelevant if a child changes writing mode, what counts is the writing mode of the element that has touch-action
15:12:54 <Patrick_H_Lauke> Patrick: in my head, it makes sense to just look at the one where you defined the touch-action explicitly
15:14:10 <Patrick_H_Lauke> Olli: it may be counterintuitive though, if I specified a certain touch action, and then one of the children changes writing mode/direction
15:14:37 <Patrick_H_Lauke> Rob: is touch-action inherited? I didn't think it is...
15:14:47 <Patrick_H_Lauke> [group checks and confirms it's not inherited]
15:15:03 <Patrick_H_Lauke> Olli: it's confusing / complex, like selection
15:15:52 <Patrick_H_Lauke> Rob: feel strongly about it, also keeping it simple
15:20:27 <Patrick_H_Lauke> PAtrick: so taking a step back, do we want this in Level 3? obviously there's no actual implementation, but just to get a sense if we decided, would browser engines even be amenable to implementing this? can mark as at risk, but we'd need some idea if we can realistically get it into engines
15:20:43 <Patrick_H_Lauke> Rob: if it works the way i think it should, then it shouldn't be too difficult to implement for Chrome
15:21:01 <Patrick_H_Lauke> [some discussion on if this were living standard there would be slightly less pressure]
15:30:01 <Patrick_H_Lauke> ACTION: group to further review https://github.com/w3c/pointerevents/pull/496 with aim to merge next meeting
15:30:18 <Patrick_H_Lauke> TOPIC: Triage unlabelled issues https://github.com/w3c/pointerevents/issues
15:34:02 <Patrick_H_Lauke> Patrick: in short, for next time, let's make sure we label all new issues to see if it's something we can do easily now, or need to defer to future
15:34:17 <Patrick_H_Lauke> ACTION: group to look at unlabelled issues for next meeting and add relevant labels/comments
15:34:36 <Patrick_H_Lauke> TOPIC: Multi-pen support and persistent pointerId #353 https://github.com/w3c/pointerevents/issues/353
15:35:04 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/pull/495
15:35:45 <Patrick_H_Lauke> Patrick: from my POV i think once i have answer regarding setting up `next` branch and merging stuff into it, then we can go ahead an merge that PR into it unless there's more work that needs to be done
15:35:56 <Patrick_H_Lauke> Olli: are there tests for this?
15:36:34 <mustaq> https://github.com/web-platform-tests/wpt/pull/46888 ?
15:36:44 <Patrick_H_Lauke> Mustaq: there are posts from wpt bot
15:37:03 <Patrick_H_Lauke> Olli: does it check that the id is actually random? that's the critical part
15:38:08 <Patrick_H_Lauke> Mustaq: those new tests are added to a new subfolder in pointer events, and that folder does not appear in WPT dashboard. should it?
15:38:12 <mustaq> https://wpt.fyi/results/pointerevents?label=master&label=experimental&aligned
15:38:52 <mustaq> The folder appears there.
15:38:54 <Patrick_H_Lauke> Mustaq: take it back, folder is there https://wpt.fyi/results/pointerevents/persistentDeviceId?label=master&label=experimental&aligned
15:39:16 <Patrick_H_Lauke> Olli: so tests pass in all browsers? that doesn't make sense since it's not implemented
15:39:34 <Patrick_H_Lauke> Mustaq: also PR had 3 files, but here i only see 2
15:39:49 <Patrick_H_Lauke> Olli: ... it's a manual test
15:41:23 <Patrick_H_Lauke> Mustaq: test checks for window.internals, and bails if not present...
15:42:00 <Patrick_H_Lauke> Olli: is that chrome-only? or is it enabled only in testing? I think the tests need to be fixed somehow
15:43:07 <Patrick_H_Lauke> Patrick: should we file issue in WPT repo?
15:43:09 <Patrick_H_Lauke> Mustaq: we should comment on the PE pull request
15:43:18 <Patrick_H_Lauke> Olli: i'll comment on it
15:44:44 <Patrick_H_Lauke> Olli: other than this it should be fine
15:45:03 <Patrick_H_Lauke> ACTION: wait to hear about fixed WPT. then we can decide to merge to next
15:45:16 <Patrick_H_Lauke> TOPIC: Meta-issue: update WPT to cover Pointer Events Level 3 #445 https://github.com/w3c/pointerevents/issues/445
15:45:38 <Patrick_H_Lauke> Olli: think we're missing only one
15:45:59 <Patrick_H_Lauke> Mustaq: I think Rob is planning to work on that one soon
15:46:33 <Patrick_H_Lauke> Olli: I think one of the issues Masayuki filed needed a new test, or there was a bug in an existing one
15:46:35 <smaug> https://github.com/w3c/pointerevents/issues/508
15:47:02 <Patrick_H_Lauke> Mustaq: I'll look into that
15:47:39 <Patrick_H_Lauke> ACTION: continue work on remaining test, Mustaq to check the issue with test raised in 508
15:48:04 <Patrick_H_Lauke> TOPIC: Touch Events - Quick update on the now-closed CG
15:52:46 <Patrick_H_Lauke> Patrick: just quick heads-up to say that CG is now closed, and final version of the TE Level 2 note has been published as Final CG Specification. there have now belatedly been some mumblings about ACTUALLY making this an official spec, and that perhaps WebApps WG may want to inherit it, but will clarify this in person at TPAC
15:52:59 <Patrick_H_Lauke> Patrick: meanwhile, thank you all as ever, and we'll reconvene in 2 weeks' time
15:53:10 <Patrick_H_Lauke> RRSAgent, make logs public
15:53:18 <Patrick_H_Lauke> RRSAgent, generate minutes
15:53:19 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/17-pointerevents-minutes.html Patrick_H_Lauke
15:53:43 <Patrick_H_Lauke> rrsagent, make logs world-visible
15:53:51 <Patrick_H_Lauke> rrsagent, bye
15:53:51 <RRSAgent> I see 4 open action items saved in https://www.w3.org/2024/07/17-pointerevents-actions.rdf :
15:53:51 <RRSAgent> ACTION: group to further review https://github.com/w3c/pointerevents/pull/496 with aim to merge next meeting [1]
15:53:51 <RRSAgent>   recorded in https://www.w3.org/2024/07/17-pointerevents-irc#T15-30-01
15:53:51 <RRSAgent> ACTION: group to look at unlabelled issues for next meeting and add relevant labels/comments [2]
15:53:51 <RRSAgent>   recorded in https://www.w3.org/2024/07/17-pointerevents-irc#T15-34-17
15:53:51 <RRSAgent> ACTION: wait to hear about fixed WPT. then we can decide to merge to next [3]
15:53:51 <RRSAgent>   recorded in https://www.w3.org/2024/07/17-pointerevents-irc#T15-45-03
15:53:51 <RRSAgent> ACTION: continue work on remaining test, Mustaq to check the issue with test raised in 508 [4]
15:53:51 <RRSAgent>   recorded in https://www.w3.org/2024/07/17-pointerevents-irc#T15-47-39