Boris Chiou
9029bddf36
In this patch, we do these things: 1. Define the mixin and dictionary based on [1]. Note that we have to make the entire mixin nullable to build IDL bindings properly. 2. Implement the parser for the keyframe offset. This includes the UTF8String, TimelineRangeOffset, and CSSNumericValue. For the tests: 1. view-timelines/get-keyframes-with-timeline-offset.html, and view-timelines/timeline-offset-in-keyframe.html depend on Bug 1810248. I have verified it by hacking the rangeStart and rangeEnd APIs on my side. 2. css/timeline-offset-keyframes-hidden-subject.html, and css/timeline-offset-keyframes-with-document-timeline.html are failed becase we don't handle the missing initial/final keyframes properly. Bug 2037642 should take care of this. 3. css/merge-timeline-offset-keyframes.html will be fixed in the following patch. [1] https://drafts.csswg.org/web-animations-2/#keyframe-offset-type Differential Revision: https://phabricator.services.mozilla.com/D306379
17 lines
693 B
INI
17 lines
693 B
INI
prefs: [layout.css.scroll-driven-animations.enabled:true]
|
|
[animate.html]
|
|
[animate() with pseudoElement parameter creates an Animation object for ::first-line]
|
|
bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1615469
|
|
expected: FAIL
|
|
|
|
[animate() with pseudoElement an Animation object targeting the correct pseudo-element for ::first-line]
|
|
bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1615469
|
|
expected: FAIL
|
|
|
|
[animate() with pseudoElement ::placeholder does not throw]
|
|
expected: FAIL
|
|
|
|
[Element.animate() correctly sets the Animation's timeline with null timeline in KeyframeAnimationOptions.]
|
|
expected:
|
|
if (os == "android") and not debug: [PASS, FAIL]
|