Repository navigation
Animate background colors on the host frame clock - #534
Merged
Merged
Conversation
This was referenced Sep 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Code OSS background transitions jumped directly to their target because WebScene did not retain or advance background color on the host frame clock. This adds bounded cold background transition state, maps the supported
backgroundalias tobackground-color, resolves fixed/currentColor endpoints, and feeds temporal RGBA to computed style and retained paint without dirtying layout.The slice reuses run/start/cancel/end events, property-removal cancellation, active frame demand, detach/display-none filtering, and idle cleanup. Authored native/browser sources cover alias matching, midpoint/reversal/final values, lifecycle events, bounded samples, and post-completion idle demand.
Only
git diff --checkran under the current implementation-first policy. Chromium/native execution, pixels, performance, allocations, lifecycle, exact Code OSS, package, and complete CI evidence remain deferred in #242.Closes #533
Progresses #242