Conversation
✅ Deploy Preview for anchor-position-wpt canceled.
|
✅ Deploy Preview for anchor-polyfill ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jgerigmeyer
approved these changes
Jun 15, 2026
jgerigmeyer
left a comment
jgerigmeyer
left a comment
Member
There was a problem hiding this comment.
Works for me! Interesting, in current Chrome (no polyfill) the popover does not scroll for me, but in current FF (also no polyfill) it does scroll with the page. Unrelated, but notable.
| }</code></pre> | ||
| </section> | ||
|
|
||
| <section id="fixed-target" class="demo-item"> |
Member
There was a problem hiding this comment.
Suggested change
| <section id="fixed-target" class="demo-item"> | |
| <section id="fixed" class="demo-item"> |
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
2 participants
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.
Description
We were always using the
absolutestrategy for Floating UI, which meant that fixed position elements were not positioned correctly. This makes the strategy dynamic, based on the positioning of the positioned element.Related Issue(s)
This relates to #350, and we should check if it fixes that.
Steps to test/reproduce
Check out position area and anchor examples