← 输入框|github.com|刷新
Skip to content

fix(core): resolve var() in css animations and keyframes per view - #11534

Open
triniwiz wants to merge 2 commits into
mainfrom
fix/css-animation-variables
Open

triniwiz wants to merge 2 commits into
mainfrom
fix/css-animation-variables

Conversation

@triniwiz

@triniwiz triniwiz commented Oct 15, 2026 •

Copy link
Copy Markdown
Member

PR Checklist

What is the current behavior?

  • Animations are built once per rule from its raw declarations, before any variable is resolved, so animation: var(--animate-spin) (how Tailwind's animate-* utilities are written) and animation-duration: var(--speed) never play.
  • A var() inside @keyframes fails to convert, and the exception stops the rest of the stylesheet from being applied.

What is the new behavior?

  • A rule whose animation declarations use variables is resolved against each view when its animations play. Rules without variables are still parsed once.
  • Keyframes whose values use variables are kept unparsed and resolved against each view when they play. Other keyframes are still parsed once.
  • Keyframes that cannot be converted are skipped with a trace warning instead of throwing.

Tests: ui/styling/css-animation-variables.spec.ts (5); four fail without the change.

Verified with all of these core PRs merged together (#11527–#11537): apps/automated passes on the iOS 26.4 simulator (1830 OK, 0 failed) and on an Android API 36 emulator (1692 OK; the one failure is the network-dependent IMAGE-CACHE.test_ImageCache_ValidUrl timeout, which also passes on reruns).

@nx-cloud

nx-cloud Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

View your CI Pipeline Execution ↗ for commit c6b7b73

Command Status Duration Result
nx test apps-automated -c=android ✅ Succeeded 3m 13s View ↗
nx run-many --target=test --configuration=ci --... ✅ Succeeded <1s View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗


☁️ Nx Cloud last updated this comment at 2026-10-15 20:41:03 UTC

@pkg-pr-new

pkg-pr-new Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@nativescript/core@11534
npm i https://pkg.pr.new/@nativescript/vite@11534
npm i https://pkg.pr.new/@nativescript/webpack@11534

commit: c6b7b73

Animations were built once per rule from its raw declarations, before
any variable was resolved, so `animation: var(--animate-spin)` (how
Tailwind's `animate-*` utilities are written) and
`animation-duration: var(--speed)` never played. A `var()` inside
`@keyframes` failed to convert and the exception stopped the rest of
the stylesheet being applied.

A rule whose animation declarations use variables, and keyframes whose
values use them, are now resolved against each view when its
animations play. Everything else is still parsed once. Keyframes that
cannot be converted are skipped with a trace warning instead of
throwing.
@triniwiz
triniwiz force-pushed the fix/css-animation-variables branch from 20397b6 to be09a7d Compare October 15, 2026 13:16

This branch has not been deployed

No deployments
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.

1 participant