16:00:51 <RRSAgent> RRSAgent has joined #pointerevents
16:00:51 <RRSAgent> logging to https://www.w3.org/2022/01/05-pointerevents-irc
16:01:33 <Patrick_H_Lauke> Meeting: PEWG
16:01:39 <Patrick_H_Lauke> Chair: Patrick H. Lauke
16:01:48 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/0d3af70c-0054-43dc-9c15-c60c5b9c3f3c/20220105T110000
16:02:04 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
16:02:56 <Patrick_H_Lauke> TOPIC: Specify event constructing steps when coalesced/predicted events are passed using the PointerEventInit #427 https://github.com/w3c/pointerevents/pull/427
16:03:15 <Patrick_H_Lauke> Olli: just making update now, figured out how to link to the definition
16:03:38 <Patrick_H_Lauke> Olli: idea is to have event construction steps in the PE spec, so somebody reading DOM spec can also follow the steps here
16:06:04 <Patrick_H_Lauke> Patrick: Rob any thoughts
16:06:09 <Patrick_H_Lauke> Rob: looks fine to me
16:06:16 <Patrick_H_Lauke> Olli: I'll make the change, then Patrick can merge
16:06:27 <Patrick_H_Lauke> ACTION: Olli to update PR, Patrick to merge once ready
16:06:41 <Patrick_H_Lauke> TOPIC: touch-action:none and overflow:auto https://github.com/w3c/pointerevents/issues/319
16:08:05 <Patrick_H_Lauke> Rob: behaviour should be easily predictable, not tied to layout, but we should put together a few examples of why it would be undesirable for overflow to change the behaviour
16:08:27 <Patrick_H_Lauke> PLH: if you could also add a test for this i'd be very happy, after you've done the example
16:08:33 <Patrick_H_Lauke> preset+ PLH
16:08:38 <Patrick_H_Lauke> present+ PLH
16:08:44 <Patrick_H_Lauke> present+ smaug
16:08:49 <Patrick_H_Lauke> present+ flackr
16:09:07 <Patrick_H_Lauke> ACTION: Rob to work on this for next meeting
16:09:34 <Patrick_H_Lauke> Patrick: we have a few left v3 issues https://github.com/w3c/pointerevents/issues?q=is%3Aissue+is%3Aopen+label%3Av3
16:14:15 <Patrick_H_Lauke> Patrick: we're at the last few issues that are non-obvious and will require quite a bit of thought. some of them seem interrelated (e.g. around pointer capture behaviours/edge cases). i would suggest there's no point now picking a new one up, and instead to adjurn for this time, making a short meeting, but then for next time around we hopefully can deal with issue #319. Rob, if you need any help or want to run something past us in
16:14:15 <Patrick_H_Lauke>  the meantime, feel free to reach out directly or in the github issue.
16:15:04 <Patrick_H_Lauke> rrsagent, set logs world-visible
16:15:09 <Patrick_H_Lauke> rrsagent, create minutes
16:15:09 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/05-pointerevents-minutes.html Patrick_H_Lauke
16:15:15 <Patrick_H_Lauke> rrsagent, set logs world-visible
16:15:47 <Patrick_H_Lauke> rrsagent, bye
16:15:47 <RRSAgent> I see 2 open action items saved in https://www.w3.org/2022/01/05-pointerevents-actions.rdf :
16:15:47 <RRSAgent> ACTION: Olli to update PR, Patrick to merge once ready [1]
16:15:47 <RRSAgent>   recorded in https://www.w3.org/2022/01/05-pointerevents-irc#T16-06-27
16:15:47 <RRSAgent> ACTION: Rob to work on this for next meeting [2]
16:15:47 <RRSAgent>   recorded in https://www.w3.org/2022/01/05-pointerevents-irc#T16-09-07