15:00:25 RRSAgent has joined #pointerevents 15:00:25 logging to https://www.w3.org/2022/06/08-pointerevents-irc 15:00:33 flackr has joined #pointerevents 15:01:40 Meeting: PEWG 15:01:46 Chair: Patrick H. Lauke 15:01:54 Agenda: https://www.w3.org/events/meetings/0d3af70c-0054-43dc-9c15-c60c5b9c3f3c/20220608T110000 15:02:05 Scribe: Patrick H. Lauke 15:02:11 ScribeNick: Patrick_H_Lauke 15:02:14 present+ smaug 15:02:19 present+ flackr 15:02:30 present+ mustaq 15:03:03 TOPIC: Recently merged: Cleanup and respec fixes https://github.com/w3c/pointerevents/pull/441 15:04:11 Patrick: all respec bugs have been fixed, and Dom has sent a PR that I merged that made further fixes to respec. so all good 15:04:26 TOPIC: New: Properties firing pointermove and pointerrawupdate https://github.com/w3c/pointerevents/pull/443 15:09:13 [reading over the changes] 15:09:47 Patrick: just confirmed that if there's *just* a change of button state (e.g. clicking mouse button making sure there's no other movement), then yes no pointermove is fired https://patrickhlauke.github.io/touch/tests/event-listener.html 15:11:52 Rob: concern about situations like drawing applications, fast movements and then lifting mouse button (?) 15:12:04 Olli: I think in practice though this will be fine 15:13:18 Rob: concerned about what happens when the change of position and button change happen exactly at the same time 15:13:40 Patrick: but they'd still be separate events 15:14:27 Olli: need to see though what button state would be in the move and the up events 15:14:37 [more discussion on the concurrent event case] 15:15:00 Rob: maybe we can define which events need to be fired when properties change (?) 15:15:10 Rob: but for this, it seems fine 15:15:14 Olli: agrees 15:15:22 ACTION: merge the PR 15:19:00 TOPIC: Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356 15:19:33 Patrick: just a heartbeat, to keep this on people's agenda 15:19:57 Patrick: no activity so far 15:20:08 Rob: maybe we can add something to our schedule to look at this 15:20:20 Mustaq: things that need to be fixed in Chrome, yes, but no progress 15:20:38 TOPIC: Side note about touch-events: Reword altitudeAngle/azimuthAngle descriptions in line with PE, add illustrations https://github.com/w3c/touch-events/pull/125 15:23:34 Patrick: just as a side note that the touch events spec now mirrors the wording used in the pointer events spec for altitudeAngle and azimuthAngle, including the diagrams. one notable difference of course is the bit where we decided to differ in PE for the default value when pen is perpendicular, so TE spec now has a matching but opposite note pointing out how it differs from PE 15:24:15 Patrick: Mustaq/Rob, you ok for next meeting to look at the further clarification about what exactly happens for concurrent move and up/down events (from our first topic)? 15:24:21 [Rob/Mustaq agree] 15:24:31 Patrick: thank you all, catch you again in two weeks' time 15:24:39 rrsagent, make logs world-visible 15:24:43 rrsagent, generate minutes 15:24:43 I have made the request to generate https://www.w3.org/2022/06/08-pointerevents-minutes.html Patrick_H_Lauke 15:24:50 rrsagent, make logs world-visible 15:25:07 rrsagent, bye 15:25:07 I see 1 open action item saved in https://www.w3.org/2022/06/08-pointerevents-actions.rdf : 15:25:07 ACTION: merge the PR [1] 15:25:07 recorded in https://www.w3.org/2022/06/08-pointerevents-irc#T15-15-22