Skip to content

Conversation

@fantasai
Copy link
Collaborator

See #8985 (comment)

In Level 2, we can change just the definition of "start time" to handle sequencing, and those adjustments will flow through the rest of the definitions appropriately.

@birtles
Copy link
Contributor

birtles commented Aug 23, 2023

I was pretty opposed to introducing two kinds of start times but I notice we already have a concept of animation effect end time so I guess this makes sense.


1. If there is a [=pending pause task=]
and [=start time=] is [=unresolved|resolved=],
and [=animation/ time=] is [=unresolved|resolved=],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this right?

Comment on lines +2644 to +2645
The <dfn for="animation effect">start time</dfn> of an [=animation effect=]
is the [=animation/start time=] of its [=associated animation=].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we define this as zero local time and say that this happens to correspond to the start time of the associated animation effect? That's how we describe the endTime API member.

I noticed we already have a definition of animation effect start time in Web Animations level 2: https://drafts.csswg.org/web-animations-2/#animation-effect-start-time

I think what we have here is compatible with that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants