- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Feb 2022 18:21:20 +0000
- To: public-css-archive@w3.org
Notes from chatting with @bramus, @mirisuzanne, and @rachelnabors: - Remove `view-timeline-fit` - Split `animation-timeline` into `animation-timeline-name` and `animation-timeline-phase`, with `animation-timeline` shorthand ``` animation-timeline-name: [ auto | none | <timeline-name> ]# animation-timeline-phase: [ active | <timeline-phase-name> ]# animation-timeline: [ <'animation-timeline-name'> <'animation-timeline-phase'> ]# ``` - Define TimelinePhase API ``` interface TimelinePhase { readonly DOMString name; readonly double startTime; readonly double endTime; } ``` - Give AnimationTimeline ability to say what TimelinePhases are in effect, e.g. by querying a Set of some kind. - ViewTimeline defines the following phases: - `entry` from when the box first comes into view from until it either is completely within view or completely covering the viewport - `exit` same, but on the other side - `contain`, while the box is fully contained within or fully covering the viewport Open Questions - Are these called phases, or something else, given we have these phases already: https://www.w3.org/TR/web-animations-1/#the-timelinephase-enumeration - How are `entry` and `exit` distinguished? Is it by writing mode of the scroll container, or are we tracking where the box originally came into view from somehow? -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7044#issuecomment-1047134956 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 21 February 2022 18:21:22 UTC