Repository navigation
Interpolate bounded foreground filters - #538
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 foreground-filter transitions jumped to their target even though WebScene could already paint the bounded filter list. This unifies parsing, transition state, computed style, and retained paint around one typed list and interpolates compatible authored-order blur/brightness/contrast/grayscale/saturate functions on the host clock, including correct identities for
none.The slice stays paint-only, preserves stacking until the final
none, emits lifecycle/cancellation events, supports reversal, releases idle demand, and accounts retained state. Authored native/browser sources include a 128-element temporal/performance contract and midpoint pixel reftest.Only
git diff --checkran under the current implementation-first policy. Chromium/native execution, pixels, performance, allocation, lifecycle, exact Code OSS, package, and complete CI evidence remain deferred. Filter keyframes and WAAPI remain outside this slice.Closes #537
Progresses #242