Chrome 144 + Firefox 147 support CSS position-anchor: none#28648
Merged
Chrome 144 + Firefox 147 support CSS position-anchor: none#28648
position-anchor: none#28648Conversation
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
8 tasks
position-anchor: none
Contributor
Implemented in chromium/chromium@351afdf (edit) Shipped in Chrome 144 apparently: chromium/chromium@f95ef29 See also: https://chromiumdash.appspot.com/commit/f95ef29e591dd8be22f22adda44a3cb179216cba |
caugner
requested changes
Dec 12, 2025
position-anchor: noneposition-anchor: none
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
caugner
approved these changes
Dec 12, 2025
Merged
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
Firefox 147 adds support for the new
nonevalue of theposition-anchorCSS property. See https://bugzilla.mozilla.org/show_bug.cgi?id=1999972.This PR adds a data point for the new value.
I've also tested it in Chrome Canary and found that it works there too. It must have been added to Chromium very recently (I can't find a PR reference or chromestatus entry), so I've put the support as "preview" for now.
AFAICT, the new value hasn't been added to the spec yet, so I've set the feature to
"standard_track": falsefor now.Test results and supporting details
Related issues