-
-
Notifications
You must be signed in to change notification settings - Fork 796
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
Misplaced Dropdown content when opened from Dialog #450
Comments
Addition: I'm experiencing the same bug with the |
The example is using the The Because the dialog uses This is a pain point of HTML/CSS, which is why I started the discussion around the See also: #265 (comment)
As for your example, you should be able to remove the
Select uses dropdown under the hood, so that's expected if you're hoisting. I'm closing this as a wontfix since this is the documented behavior. |
Thank you for this detailed answer! Totally missed that in the docs. It just felt like a regression as this was (unexpectedly?) working fine up to 2.0.0-beta.41. |
I didn't realize this worked before. I took another look and realized I missed something the first time around.
I was mistaken here...I should have said "because the dialog uses However, the translate is only used for show/hide animations. As such, they're not necessary to keep on the dialog after it shows. By removing TL;DR – this will work as expected again in beta.43. |
Great news, thanks for looking into this again! 👏🏻 😍 |
I can confirm this is working again in 2.0.0-beta.43. Thank you! |
Describe the bug
When
sl-dropdown
is placed into asl-dialog
, the dropdown content is mispositioned. I observed this since 2.0.0-beta.42.To Reproduce
https://jsfiddle.net/devmount/oz3c6v8k/
Expected behavior
I expect the dropdown content right next to the dropdown field without a large gap in between.
Screenshots
![image](https://user-images.githubusercontent.com/5441654/120189041-24100c80-c217-11eb-85ee-22bbf97620fe.png)
Desktop (please complete the following information):
Additional context
Maybe related to #449
The text was updated successfully, but these errors were encountered: