-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Inputs, Menu: Standardize default origin point #10071
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
Conversation
This reverts commit da61be9.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #10071 +/- ##
==========================================
- Coverage 91.14% 91.13% -0.01%
==========================================
Files 411 411
Lines 12482 12481 -1
Branches 2422 2422
==========================================
- Hits 11377 11375 -2
Misses 560 560
- Partials 545 546 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
I guess only @Garderoben knows why That being said, I have noticed this and it has perplexed me on all components where the dropdown opens over the component itself. I just never questioned @Garderoben's knowledge of how it should be. |
Lets make it consistent across the library and change it |
@danielchalmers when you merge this, please don't forget to update the v8 migration guide |
Was added to #9953 (comment) |
This commit broke the select: |
Description
The default origin points for input popovers aren't consistent. This makes them industry standard.
Autocomplete opens one way
Select a different way
Material Design 2
How Has This Been Tested?
visually
Type of Changes
Date picker:
Menu
Checklist
dev
).