Pickers: Fix popover elevation and gap#10270
Conversation
|
Tested visually briefly, needs confirmation that it fixes the issues mentioned. If any further refactoring or unit tests is wanted, kindly edit the branch. |
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #10270 +/- ##
==========================================
- Coverage 91.53% 91.51% -0.02%
==========================================
Files 414 414
Lines 12989 12988 -1
Branches 2452 2452
==========================================
- Hits 11889 11886 -3
Misses 555 555
- Partials 545 547 +2 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
|
Did not check the PR yet, but found another regression by this PR;#9993 (comment)
|
Want to help to test it visually @jperson2000? |
You bet. It looks like we're testing all popovers after this change. Here's what I see for components when I test this branch: MudAutoCompleteI see the 20px top margin is now fixed. MudColorPickerI see the 20px top margin is now fixed. MudDatePickerI see the 20px top margin is now fixed. MudDateRangePickerI see the 20px top margin is now fixed. Despite the 3px whitespace between the line and the popover, the popover really is adjacent to the date range picker. MudPopoverI see good alignments in the "popoverception" example. MudSelectI see the 20px top margin is now fixed. MudTimePickerI see the 20px top margin is now fixed. Looks good to me! Anything else I can help test? |
What about the arrows? |
|
Thank you @jperson2000 !
@ScarletKuro Good catch, I'll take care of that in a second PR |
Ok, merging then |










Description
Regression by: #9993
Resolves #10235
mud-picker-popoverclass to the popoverMudPicker.Elevationis now nullableMudGlobal.PopoverDefaults.Elevationfor inline pickers0for other variants8; you couldn't use that number to add an elevation for other variantsAdditionally resolves issue caused by #10071 where there was a (now no longer needed) margin between the picker input and the picker itself:
This PR may or may not be considered a breaking change.
How Has This Been Tested?
visually
Type of Changes
Checklist
dev).