[scroll-animations-1][web-animations-2] getAnimations should return scroll animations which haven't ticked yet.

[flackr]

In web-animations-1, getAnimations is defined to return the list of relevant animations, most notably where the associated effect is current or in effect. The intent is to not need to return animations which will no longer having an affect on the element. Animations which will later have an effect are still considered current.

Scroll-linked animations are not current or in effect due to an inactive time when:

• They have just been constructed and have not sampled the scroll position yet, see avoiding cycles with layout. See repro in crbug.com/1356542
• The scroller is not currently scrollable

In both of these cases, I think developers would expect the animation to still be considered relevant as it may later have an effect, just as they also expect an animation which has been delayed to be returned by getAnimations.

I propose these animations should be considered to be current, as the definition for current suggests it includes any animation which may become in play. This would mean:

• These animations would be listed in getAnimations per web-animations-1 6.8
• Animated properties will act as if will-change is specified per web-animations-1 5.6.

Concretely the change could be adding "If has finite timeline is true" to the list of conditions under which an animation is considered to be current.