Generate effective CSS property metadata - #309
Merged
Merged
Conversation
75 tasks
This was referenced Sep 17, 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.
Summary
Performance boundary
High-frequency direct fields still return before metadata lookup. Common margin/padding/gap/overflow shorthands retain their existing direct application paths. Only six previously incorrect logical shorthands expand during ordinary application; rollback continues to expand only on the rare rollback path.
Identical AppleClang 21
-O3A/B over 24 million mixed property-mask lookups: 502.446 ms baseline median versus 424.271 ms candidate median (-15.56%).Validation
This is the property-metadata stage of #235. It intentionally does not touch #238 Linux timing attribution or #297 stylesheet-finalization work.