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
Describe the bug
In cases where the select's dropdown menu is shown over components with higher z-indexes, it can get hidden by this another component (see screenshot)
Expected behavior
Select's dropdown menu always on top.
Screenshots
Additional context Question: why was the z-index = 1 and 2 needed for the NumericStepper?
Anyway, we probably agree that the menu portal should be always over any other component.
The text was updated successfully, but these errors were encountered:
Maybe for most cases, but, for example, should not be over a modal component IMO.
Makes sense, but I'm talking only about the dropdown menu. So, if a Select is under a modal, it will be closed anyway (clicking outside the dropdown for opening a modal, for instance, would automatically close it).
Nice! I just thought the sentence was ambiguous because dropdowns that are outside the modal should not be over the overlay, of course. But I get your point :)
Describe the bug
In cases where the select's dropdown menu is shown over components with higher z-indexes, it can get hidden by this another component (see screenshot)
To Reproduce
Change the Single Select example
to
Expected behavior
Select's dropdown menu always on top.
Screenshots
Additional context
Question: why was the
z-index = 1 and 2
needed for theNumericStepper
?Anyway, we probably agree that the menu portal should be always over any other component.
The text was updated successfully, but these errors were encountered: