Update css-anchor-positioning for a Safari bug#7387
Open
pomerantsev wants to merge 1 commit intoFyrd:mainfrom
Open
Update css-anchor-positioning for a Safari bug#7387pomerantsev wants to merge 1 commit intoFyrd:mainfrom
pomerantsev wants to merge 1 commit intoFyrd:mainfrom
Conversation
Adds a link to a reproduction. The bug is currently fixed in Safari Technology Preview, so I didn't file a webkit bug. In the real world, the library I'm maintaining has to do browser sniffing because some of its functionality is broken due to this bug with anchor positioning in Safari: https://github.com/pomerantsev/accented/blob/4312cae5b4dde15b09806e84b3ced3e18ea997ac/packages/accented/src/utils/supports-anchor-positioning.ts#L1-L8
a8032de to
5c9184b
Compare
pomerantsev
commented
Oct 6, 2025
| "1":"Can be enabled via the `#enable-experimental-web-platform-features` flag in `chrome://flags`", | ||
| "2":"Can be enabled using the `layout.css.anchor-positioning.enabled` flag. Enabled by default in Firefox Nightly only" | ||
| "2":"Can be enabled using the `layout.css.anchor-positioning.enabled` flag. Enabled by default in Firefox Nightly only", | ||
| "3": "There's a [bug with `position: fixed` and non-initial containing blocks](https://codepen.io/pavelp/pen/KwVPrrB)." |
Author
There was a problem hiding this comment.
I'm not sure if a link to a personal codepen is appropriate here, so I'm happy to use it as a conversation starter and discuss what a more durable alternative could be if this change is overall acceptable.
pomerantsev
added a commit
to pomerantsev/accented
that referenced
this pull request
Dec 20, 2025
Anchor positioning in Safari 26.0 was buggy (see Fyrd/caniuse#7387), so I had to create a special case to never use anchor positioning in that browser. Now the bugs are fixed, and Accented no longer supports 26.0, so it's time to retire this special case.
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.
Adds a link to a reproduction.
The bug is currently fixed in Safari Technology Preview, so I didn't file a webkit bug.
In the real world, the library I'm maintaining has to do browser sniffing
because some of its functionality is broken due to this bug with anchor positioning in Safari:
https://github.com/pomerantsev/accented/blob/4312cae5b4dde15b09806e84b3ced3e18ea997ac/packages/accented/src/utils/supports-anchor-positioning.ts#L1-L8