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
Having a sl-select in a parent element with container-type set to something different then normal leads to the listbox of the select no longer rendering over other elements (which are not part of the container-type parent).
This seems to be a problem with the sl-popup. Because this behavior can also be achieved with the popup ( which is also used in the select)
I'm not sure, if this is even fixable in the component itself, or if it is something, which the user of the sl-select has to be taken care of.
The container-type is creating a new stacking context. If adding position: relative and z-index:1 (or some higher z-index, that the other elements outside of the container-type element has), the rendering is done correctly again.
The text was updated successfully, but these errors were encountered:
Here's like a minimal reproduction of how container-type makes a new "stacking context", our form controls do have position: relative;and so they roughly mirror the issue you see in the codepen below:
Describe the bug
Having a sl-select in a parent element with
container-type
set to something different thennormal
leads to the listbox of the select no longer rendering over other elements (which are not part of thecontainer-type
parent).This seems to be a problem with the sl-popup. Because this behavior can also be achieved with the popup ( which is also used in the select)
To Reproduce
Screenshots
Browser / OS
Additional information
I'm not sure, if this is even fixable in the component itself, or if it is something, which the user of the sl-select has to be taken care of.
The
container-type
is creating a new stacking context. If addingposition: relative
andz-index:1
(or some higher z-index, that the other elements outside of thecontainer-type
element has), the rendering is done correctly again.The text was updated successfully, but these errors were encountered: