-
-
Notifications
You must be signed in to change notification settings - Fork 11
Alternate overflow options #318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for anchor-polyfill ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for anchor-position-wpt canceled.
|
strategy: 'absolute', | ||
} as unknown as MiddlewareState, | ||
{ | ||
boundary: offsetParent, | ||
rootBoundary: 'document', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As context, if I recall correctly, I was being overly explicit in this call, but it turns out these options are not always correct, and the defaults are actually what we want.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me!
Probably unrelated, but I notice in my Chromium browser (no polyfill) that the last successful fallback "sticks" even if scrolled to allow a prior fallback to no longer overflow. Is that a bug, or a change in the spec?
I've noticed this as well. I opened #325 to track this. |
Description
Overflow checking was not working as expected for
position-try-fallbacks
with the viewport as the containing block.Related Issue(s)
#317
Steps to test/reproduce