You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several tests that expect animations with named timelines that are unattached (ie animation-timeline: none, etc) to hold their time at zero. The spec says for the case where a named timeline isn't found, "Otherwise the animation is not associated with a timeline", which implies that the animation should have a null timeline and the animation should not have a resolved time (and shouldn't show up in getAnimations() either). Tests that I have found that expect this behavior:
There are several tests that expect animations with named timelines that are unattached (ie
animation-timeline: none
, etc) to hold their time at zero. The spec says for the case where a named timeline isn't found, "Otherwise the animation is not associated with a timeline", which implies that the animation should have a null timeline and the animation should not have a resolved time (and shouldn't show up in getAnimations() either). Tests that I have found that expect this behavior:The text was updated successfully, but these errors were encountered: