You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use Style="width:150px" on some MudDatePickers which just shrank the input portion and left the picker itself the same. After 7.0.0 preview the input and picker are now both constrained to 150px which breaks the picker visually.
The new 7.X.X behavior might actually be the intended way, and I should probably just constrain the parent of the MudDatePicker which works correctly on 7.X.X. Thoughts on this @henon and team? Or is there a better way to adjust the input portion already? Thanks
@danielchalmers do you have an idea which PR is responsible for this change in behavior? I am not saying it is necessarily bad behavior, it needs to be determined.
@digitaldirk Could you do a git bisect to find the exact commit? It is fairly easy and requires about half an hour of compiling five to seven different commits that bisect checks out for you.
Bug type
Component
Component name
MudDatePicker
What happened?
I use
Style="width:150px"
on someMudDatePicker
s which just shrank the input portion and left the picker itself the same. After 7.0.0 preview the input and picker are now both constrained to 150px which breaks the picker visually.The new 7.X.X behavior might actually be the intended way, and I should probably just constrain the parent of the
MudDatePicker
which works correctly on 7.X.X. Thoughts on this @henon and team? Or is there a better way to adjust the input portion already? Thanks7.X.X behavior:
6.X.X behavior:
7.X.X behavior with constrained parent:
Expected behavior
Same behavior as 6.X.X
Reproduction link
Reproduction steps
Relevant log output
No response
Version (bug)
7.X.X preview
Version (working)
6.X.X
What browsers are you seeing the problem on?
Firefox, Chrome, Edge
On which operating systems are you experiencing the issue?
Windows
Pull Request
Code of Conduct
The text was updated successfully, but these errors were encountered: