Skip to content

Chrome 146 scroll-triggered animations#29034

Draft
chrisdavidmills wants to merge 1 commit intomdn:mainfrom
chrisdavidmills:chrome-146-scroll-triggered-animations
Draft

Chrome 146 scroll-triggered animations#29034
chrisdavidmills wants to merge 1 commit intomdn:mainfrom
chrisdavidmills:chrome-146-scroll-triggered-animations

Conversation

@chrisdavidmills
Copy link
Contributor

@chrisdavidmills chrisdavidmills commented Feb 12, 2026

Summary

Chrome 146 adds support for scroll-triggered animations; see https://chromestatus.com/feature/5181996801982464.

The latest Chrome collector PR has added BCD for several of the related features; my PR adds a few more, namely the <animation-action> data type, and the related range properties, which are supported but currently under an old name.

Test results and supporting details

Related issues

@github-actions github-actions bot added data:css Compat data for CSS features. https://developer.mozilla.org/docs/Web/CSS size:l [PR only] 101-1000 LoC changed labels Feb 12, 2026
@github-actions
Copy link
Contributor

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

Copy link
Contributor

Choose a reason for hiding this comment

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

We discussed support data for CSS types in the BCD meeting on 2026-01-20 and the consensus was to record support data under the individual CSS properties instead of for the CSS type itself. The guidelines are yet to be written though: #28913

CSS types are a bit like mixins, so even though all the properties here likely support the same values for <animation-action>, it is better to actually test using the collector. I'll add the "needs collector test" label.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

OK, I'll wait for #29033 to be merged before doing anything about this.

I agree that CSS types are a bit like API mixins, but unlike mixins, we document CSS types on their own separate pages.

@caugner caugner added the needs collector test Needs a custom BCD collector test label Feb 13, 2026
@chrisdavidmills chrisdavidmills marked this pull request as draft February 17, 2026 08:45
@chrisdavidmills
Copy link
Contributor Author

Setting this to draft status for now, as the range properties have the wrong names. They were recently renamed in a CSS WG resolution (see w3c/csswg-drafts#13174 and w3c/csswg-drafts#13307), which hasn't made it to the spec yet. Chromium supports them using the latest correct names, so there is no need for alternative names here.

I'll correct these when the spec has been updated.

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

Labels

data:css Compat data for CSS features. https://developer.mozilla.org/docs/Web/CSS needs collector test Needs a custom BCD collector test size:l [PR only] 101-1000 LoC changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments