Chrome 132 supports anchor-size() on margin and inset properties #25443
Conversation
This file contains 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
github-actions
bot
added
data:css
Merged
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
Chrome 132 supports the
anchor-size()function on inset (e.g.inset,top,bottom, and logical equivalents) and margin (e.g.margin,margin-top,margin-left, and logical equivalents) properties.This PR adds a data point for
anchor-size()to each of those properties, and a data point toanchor-size()itself to mention inset and margin property support.Test results and supporting details
See https://chromestatus.com/feature/5203950077476864 for the data source.
I've also tested
anchor-size()in all the different inset and margin properties, with varying combinations of arguments (including<anchor-name>,<anchor-size>, and fallback<length-percentage>values) and as part ofcalc()expressions, in Chrome 132/133. They seemed to work as expected, and I didn't notice any bugs or support weirdness.Related issues