Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

uthem150
Copy link
Contributor

What this fixes

When CSS custom properties (like --my-variable) fail to animate on the compositor, they get lumped together with regular CSS properties in the error message. This is confusing because they fail for different reasons.

Changes

Before/After

Before: Unsupported CSS Properties: --swing-y, color
After: Two separate messages explaining what went wrong

Closes #14521

@uthem150 uthem150 requested a review from a team as a code owner August 10, 2025 10:06
@uthem150 uthem150 requested review from paulirish and removed request for a team August 10, 2025 10:06
Copy link

google-cla bot commented Aug 10, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link
Collaborator

@connorjclark connorjclark left a comment

Choose a reason for hiding this comment

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

thanks!

@connorjclark connorjclark merged commit e67b897 into GoogleChrome:main Aug 28, 2025
25 checks passed
@uthem150
Copy link
Contributor Author

Thanks for merging this! Glad to help improve the developer experience.

@uthem150 uthem150 deleted the fix/non-composited-custom-properties branch August 29, 2025 05:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

add new UIString for non-composited-animations due to custom properties
2 participants