Open Bug 1676779 (scroll-animations-1) Opened 5 years ago Updated 1 day ago

[meta] Implement Scroll-driven Animations

Categories

(Core :: Layout, enhancement)

Product:
Core
Component:
Layout
Type:
enhancement

Tracking

()

People

(Reporter: hiro, Unassigned)

References

(Depends on 33 open bugs, Blocks 7 open bugs,
URL
)

Details

(Keywords: meta, parity-chrome, parity-safari)

I am filing this new meta bug rather then re-using bug 1281348 for the new scroll animations since the new spec provides two different way to generate scroll linked animations, generating by JS, or generating by CSS, but we are not going to implement the JS way right now since it requires types defined in the CSS typed OM spec, we are going to implement the CSS way right now.

That's said, this bug will be a meta bug to track the both way, I am going to file those bugs respectively.

Depends on: js-scroll-driven-animations
Keywords: meta
Depends on: 1731112
Depends on: 1762238
Depends on: 1762237
No longer depends on: 1762238
Depends on: 1786448
Depends on: 1791884
Blocks: all-css-modules
Summary: [meta] scroll linked animations → [meta] Implement Scroll-linked Animations
Depends on: 1807685

(hiro: maybe we should update the title and alias of this bug, given the spec rename in https://github.com/w3c/csswg-drafts/issues/8101 (see also bug 1807685)?)

Flags: needinfo?(hikezoe.birchill)

(same goes for bug 1676780 and bug 1676781 I guess)

Flags: needinfo?(hikezoe.birchill)
Summary: [meta] Implement Scroll-linked Animations → [meta] Implement Scroll-driven Animations
Alias: scroll-linked-animations → scroll-driven-animations
Depends on: 1841005

Update alias to match the spec link: scroll-animations-1

Alias: scroll-driven-animations → scroll-animations-1
Depends on: 1817303
Depends on: 1943409
Depends on: 1825427
Depends on: 1946570
Depends on: 1960524
Blocks: 1973499
Depends on: 1974129
Depends on: 1980789
Depends on: 1978491
No longer depends on: 1825427
Depends on: timeline-ranges
Depends on: 1737927
Depends on: 1997436
Depends on: 1992772
Depends on: 2000461
Blocks: 2000918
Depends on: 2005347
Depends on: 2005862
Depends on: 2006258
Depends on: 2007638
No longer blocks: 1962108
Depends on: 1324602
Depends on: 2015188
Depends on: 2015190
Depends on: 2015191
Depends on: 2020824
Blocks: 2021610
Depends on: 2022727
Blocks: 2022820
Depends on: 2023599
Blocks: 2024017
Depends on: 2024336
Depends on: 2024744
Depends on: 2025057
Depends on: 2023455
Depends on: 2021952
No longer depends on: 2023455
Depends on: 2027832
Blocks: 2025984
No longer blocks: 2022820
Depends on: 2039350
Depends on: 2039572
Depends on: 2039708
Depends on: 2040536
Depends on: 2041874
No longer depends on: 1974129
Depends on: 2042876
Depends on: 2044726
Depends on: 2044865
Depends on: 2047032
Depends on: 2047034
Depends on: 2051972
No longer depends on: 2051972
Depends on: 2053281
Blocks: 2053023
Duplicate of this bug: 1293571
Blocks: 2055350
Depends on: 2055780
Depends on: 2057016
Depends on: 2060669
Depends on: 2064481
Blocks: 2067256
Blocks: 2067191
Blocks: 2064948

Any forecast when does this get enabled by default?

I'm not the implementer, but you should follow bug 1324602, which is meant to enable this feature by default.
And according to the meta info in bug 2017354, this is planned for October, but Boris will know better.

Sebastian

Flags: needinfo?(boris.chiou)

Yes. We are planning to enable it by default in October or in the beginning of November this year, after we fixed all the (interop-related) WPT failures and stability issues.

Flags: needinfo?(boris.chiou)
Depends on: 2071367
Depends on: 1321405
No longer depends on: 1321405
No longer depends on: 1817303
No longer depends on: 1324602
Depends on: 1324602
You need to log in before you can comment on or make changes to this bug.