Re: [csswg-drafts] [css-animations-2][web-animations-2] (proposal) Add pointer driven animations (#10574)

The CSS Working Group just discussed `[css-animations-2][web-animations-2] (proposal) Add pointer driven animations`, and agreed to the following:

* `RESOLVED: Start pointer-animations-1`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> ydaniv: at TPAC I presented a proposal for pointer-timeline<br>
&lt;emilio> ... which allows setting an element / portion / whole viewport as the timeline for attaching an animation<br>
&lt;emilio> ... since then the resolution was to put this up for review<br>
&lt;emilio> ... it got several thumbs up<br>
&lt;emilio> ... I think q is whether it's time to start a draft<br>
&lt;kizu> +1<br>
&lt;bramus> +1<br>
&lt;ntim> q+<br>
&lt;emilio> TabAtkins: I saw a lot of questions, but let's start a draft, we can answer questions as we go along<br>
&lt;TabAtkins> +1<br>
&lt;astearns> ack ntim<br>
&lt;emilio> ntim: I wonder if there's opportunity with innovation there<br>
&lt;emilio> ... you know, replacing the page slide gesture with pointer-timeline<br>
&lt;emilio> ... a bit of a tangent<br>
&lt;emilio> ydaniv: for now pointermove<br>
&lt;bramus> q+ seems view-transitions related<br>
&lt;emilio> ... is mapped to legacy tap<br>
&lt;emilio> ... this doesn't overlap with touchmove or swipes<br>
&lt;astearns> ack seems<br>
&lt;astearns> ack view-transitions<br>
&lt;emilio> ... seems consistent that on touch devices just tapping makes the animation jump into that position<br>
&lt;astearns> ack related<br>
&lt;flackr> q+<br>
&lt;emilio> ... up to further issues for touch<br>
&lt;emilio> ... but I think it's current state of things<br>
&lt;emilio> ... and how pointermove interacts on touch devices<br>
&lt;emilio> bramus: just to clarify are you talking about the navigate back / forward gesture on touch?<br>
&lt;emilio> ... seems related to view-transitions<br>
&lt;emilio> ... where in the future we optionally have as you slide you can trigger that gesture<br>
&lt;emilio> s/that gesture/ a view transitoin<br>
&lt;emilio> ntim: it seems the swipe is linked to the timeline<br>
&lt;emilio> ... as you swip you can cancel the swipe<br>
&lt;emilio> bramus: the view transition would use that swipe mechanism to drive the transition<br>
&lt;emilio> ydaniv: so not related<br>
&lt;emilio> ntim: just making sure we're not building separate mechanisms for the same things<br>
&lt;emilio> q?<br>
&lt;emilio> ack flackr<br>
&lt;astearns> ack flackr<br>
&lt;emilio> flackr: one clarification, we send pointermove for touch move<br>
&lt;emilio> ... is mousemove only for tabs<br>
&lt;emilio> ... so that needs to be clear<br>
&lt;emilio> ... re. swipes<br>
&lt;astearns> s/tabs/taps/<br>
&lt;emilio> ... when we're handling swipes we want a fling<br>
&lt;emilio> ... which generates motion the finger didn't actually move<br>
&lt;ydaniv> s/tabs/taps/<br>
&lt;emilio> ... I don't think pointer timelines want quite that<br>
&lt;emilio> ... most use cases want to just respond to current pointer pos<br>
&lt;bramus> +1<br>
&lt;emilio> astearns: other questions?<br>
&lt;emilio> PROPOSED: ydaniv to start a draft on pointer-driven animations, name TBD when we publish<br>
&lt;emilio> ydaniv: pointer-animations-1?<br>
&lt;emilio> astearns: sounds good<br>
&lt;emilio> emilio: consistent with scroll-animations right?<br>
&lt;emilio> ydaniv: yes<br>
&lt;emilio> RESOLVED: Start pointer-animations-1<br>
&lt;emilio> \o/<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10574#issuecomment-2628585331 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 31 January 2025 23:54:17 UTC