Chrome 131 removed inset-area #25475
Merged
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
caugner
commented
Jan 3, 2025
There was a problem hiding this comment.
Just tested that Chrome 130 shows a deprecation warning:
Chrome 131 no longer shows this warning.
Interestingly, setting inset-area does not set position-area in either versions, but the bottom line is that the deprecated property seems to have been removed in Chrome 131.
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 131 removed
inset-area, the old name ofposition-area.Test results and supporting details
This commit mentions it: chromium/chromium@36e8cec
Computed properties no longer returns it: caugner/css-properties@7f36097
Related issues