-
Notifications
You must be signed in to change notification settings - Fork 76
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
fix(dropdown): fix calculation of max-items for non-Chromium browsers. #5677
fix(dropdown): fix calculation of max-items for non-Chromium browsers. #5677
Conversation
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.
Nice! A one liner!
Guess we need to start getting screenshots on other browsers :)
Yeah, we can reconsider expanding our coverage in the near future. Maybe for starters we can add screenshots for non-Chrome fixes? cc @benelan |
+1 |
Yeah Chromatic supports Firefox, I'll look to see if there is a way to specify which browser to run on per snapshot |
That would be very cool if that's possible. |
Unfortunately it's not possible. We would have to run all snapshots on both chrome and firefox in order to add coverage for the non-Chrome fixes. Could be a candiate for our first official enhancement request |
Had a feeling that was the case. Certainly would make for a great experience though if we could add browser-specific snapshots since we do get reports on specific UI issues that would be excellent to capture with just a single or small set of very specific cases that are browser-specific. We should definitely request this feature. |
Related Issue: #5663
Summary
This fixes a regression caused by #5399 where the floating-ui element is placed offscreen and its styles change the offsetParent in non-Chromium browsers.
This codepen shows the difference when opened in Chromium vs non-Chromium browsers: https://codepen.io/jcfranco/pen/OJEMwzz?editors=1010