My gif creator did not work well this time but see below

Problem

Fix

Example for 8656, There's another one I fixed but I lost the # while working.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.48%. Comparing base (ac1d69c) to head (627ffa5).
Report is 10 commits behind head on dev.

@@            Coverage Diff             @@
##              dev   #10327      +/-   ##
==========================================
- Coverage   91.54%   91.48%   -0.07%     
==========================================
  Files         415      416       +1     
  Lines       13017    13054      +37     
  Branches     2457     2473      +16     
==========================================
+ Hits        11917    11943      +26     
+ Misses        549      548       -1     
- Partials      551      563      +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

What about merging these into a single parameter public DropDownBehavior DropdownBehavior { get; set; } with

public struct DropdownBehavior {
  public bool Fixed { get; set; }
  public OverflowBehavior OverflowBehavior { get; set; } = OverflowBehavior.FlipOnOpen;
}

Alternative names DropdownSettings, PopoverBehavior or PopoverSettings.

I think for this very specialized configuration preparing the settings object in@code and passing it like such <MudAutocomplete DropdownSettings="@settings"> is no big deal.

In addition to that the parameters intended for the popover are now intuitively named which is not the case when they are directly exposed in MudAutocomplete on their own. I when first seeing this I wasn't sure what <MudAutocomplete Fixed="true"> would mean.

I think for MudSelect there is potential for a future breaking change (i.e. v9) to move these placement properties into the new parameter as well.

Maybe then we can expand this example with the new options as well

Please name it DropDownSettings so we are not limited to behavioral settings.

Sorry for being a PITA, just think DropdownSettings would be best (no capitalization of Down)

Sorry for being a PITA, just think DropdownSettings would be best (no capitalization of Down)

Well I'll be a monkey's uncle! Give me 5.

and maybe 5 more, have to write unit tests

Let me know if you want any additional changes, I hear PopoverSettings is hot right now :)

LGTM, thanks for your patience ;). @ScarletKuro you may merge this if you agree with the changes.

The original problem that I initially reported on discord is fixed, but I see that in Edge if you open a very high inspector, this part is sticking out:

Is it something that is possible to fix? Should we just merge this PR and leave this problem for other PR?

LGTM, thanks for your patience ;). @ScarletKuro you may merge this if you agree with the changes.

The original problem that I initially reported on discord is fixed, but I see that in Edge if you open a very high inspector, this part is sticking out: Is it something that is possible to fix? Should we just merge this PR and leave this problem for other PR?

I'm sure it is, probably related to appbar.razor which I had to change for the new properties so I don't see a problem with adding it to this PR. give me a few to confirm and I'll submit if I'm correct.

Actually no, it all appears to be working by design. I can only see the overlap if I zoom to 200% and browser zoom can be odd anyways. I can replicate on chrome if I zoom high enough (500%), Same with firefox (220%). Unless there is some other way to replicate.

Actually no, it all appears to be working by design. I can only see the overlap if I zoom to 200% and browser zoom can be odd anyways. I can replicate on chrome if I zoom high enough (500%), Same with firefox (220%). Unless there is some other way to replicate.

Hmm weird, I don't need to zoom anything. I have 2k monitor and all I have to do is to open inspector on like half of the screen size for it to stick out.
@danielchalmers should we bother about it?

@ScarletKuro it's an old issue #8657

@ScarletKuro it's an old issue #8657

Ok, lets merge then.