Repository navigation
Skip identical CSS custom-property recascade - #550
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.
Closes #549. Advances #243 and #235.
Exact repeated nonempty CSS custom-property writes now compare the authored token and priority before mutation, so unchanged Code OSS style updates preserve notification/diagnostic behavior while avoiding unnecessary subtree recascade, layout, and scene scheduling. Different values, importance changes, and removals retain existing invalidation.
Validation intentionally deferred under the current fast-merge instruction:
git diff --checkpassed; 4,096-write connected/detached zero-work and reconnect lifecycle regressions were authored but not executed. Dynamic Code OSS A/B, package, visual, and performance evidence remains in #243.