Skip to content
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

MudMenu and MudSelect rendering multiple popovers #3249

Closed
1 of 2 tasks
jhoran1046 opened this issue Nov 3, 2021 · 4 comments
Closed
1 of 2 tasks

MudMenu and MudSelect rendering multiple popovers #3249

jhoran1046 opened this issue Nov 3, 2021 · 4 comments

Comments

@jhoran1046
Copy link

Bug type

Component

Component name

MudSelect and MudMenu

What happened?

After upgrading to 5.2.0 I am having an issue with the MudSelect and MudMenu components. They are producing double popovers. One seems to be anchored to the component and another that seems to be anchored to the top MudAppBar.

Expected behavior

The expected behavior is that the MudSelect and MudMenu open with only one popover that is anchored in the correct location with the specified width
MudSelectStart
DoubleDropDownSelector
DoubleMenu

Reproduction link

https://try.mudblazor.com/snippet/QYGbFbudKouNVGIb

Reproduction steps

  1. Navigate to page with component and activate it
  2. Component then displays a popover anchored to the component and another one that is anchored to something else and is the whole width of the page

Relevant log output

none

Version (bug)

5.2.0

Version (working)

5.1.5

What browsers are you seeing the problem on?

Chrome, Microsoft Edge

On what operating system are you experiencing the issue?

Windows

Pull Request

  • I would like to do a Pull Request

Code of Conduct

  • I agree to follow this project's Code of Conduct
@JonBunator
Copy link
Member

JonBunator commented Nov 3, 2021

Are you maybe using <MudThemeProvider\> multiple times?

@Garderoben
Copy link
Member

You have more than one <MudThemeProvider\>

@jhoran1046
Copy link
Author

That was the issue. There was one in MainLayout.razor and one in App.razorThis situation has existed in our application for several months and did not present itself until the upgrade to 5.2.0. I spent several hours looking for other causes and was able to reproduce it on the try.mudblazor.com site and the issue went away when I downgraded to the previous version.

Why am I able to reproduce it here? https://try.mudblazor.com/snippet/QYGbFbudKouNVGIb

I apologize for wasting anyone's time because I believe I have seen this some place before and I should have checked.
image

@JonBunator
Copy link
Member

Why am I able to reproduce it here? https://try.mudblazor.com/snippet/QYGbFbudKouNVGIb

I think the problem is that try.mudblazor adds a ThemeProvider for each .razor file. We should fix this

I apologize for wasting anyone's time because I believe I have seen this some place before and I should have checked. image

No worries :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants