Skip to content

[animation-trigger] Parse timeline-trigger-name #53598

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 4, 2025

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

The new plan for animation-trigger is that it will specify a dashed
ident which identifies a trigger that is named by a timeline-trigger
property whose timeline-trigger-name is a matching dashed ident.

The parsing test is added to a new
scroll-animations/animation-trigger/parsing as a way of keeping all
animation-trigger related test as close as possible.

Over the next couple of patches we will implement the following
properties:

  • timeline-trigger-behavior,
  • timeline-trigger-range-start,
  • timeline-trigger-range-end,
  • timeline-trigger-exit-range,
  • timeline-trigger-exit-range-end
  • timeline-trigger (shorthand)

Then, we will switch animation-trigger over to using dashed idents,
delete the other animation-trigger-* properties, and then port all
related tests to using timeline-trigger.

Bug: 429392773, 390314945
Change-Id: I2dde943a1becfd24f3ff643b7fa4d2cc12fbbcde
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6702431
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: David Awogbemila <awogbemila@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1482671}

The new plan for animation-trigger is that it will specify a dashed
ident which identifies a trigger that is named by a timeline-trigger
property whose timeline-trigger-name is a matching dashed ident.

The parsing test is added to a new
scroll-animations/animation-trigger/parsing as a way of keeping all
animation-trigger related test as close as possible.

Over the next couple of patches we will implement the following
properties:
- timeline-trigger-behavior,
- timeline-trigger-range-start,
- timeline-trigger-range-end,
- timeline-trigger-exit-range,
- timeline-trigger-exit-range-end
- timeline-trigger (shorthand)

Then, we will switch animation-trigger over to using dashed idents,
delete the other animation-trigger-* properties, and then port all
related tests to using timeline-trigger.

Bug: 429392773, 390314945
Change-Id: I2dde943a1becfd24f3ff643b7fa4d2cc12fbbcde
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6702431
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: David Awogbemila <awogbemila@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1482671}
Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

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

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot merged commit 35daf31 into master Jul 4, 2025
24 checks passed
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cf39d1d90c branch July 4, 2025 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants