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
Hello together, thanks in advance for your support :)
The issue is present in the latest release.
I have searched the issues of this repository and believe that this is not a duplicate.
Current Behavior 😯
when trying to use the Autocomplete component from Material UI, I face an issue with wrong position of the drop down while scrolling. The drop down has a fixed position and is not set under the text field of Autocomplete. The Autocomplete is used inside a web component. Do you have an idea, what it could be? Think nested scroll views are a big issue here. This behaviour seems to be for me as a bug. Issue is in chrome as well in firefox.
Expected Behavior 🤔
The position of the drop down from auto complete should remain if I scroll the "outer" ScrollView.
Steps to Reproduce 🕹
Steps:
use two ScrollViews => the inner in a web component, the outer could be normal
The text was updated successfully, but these errors were encountered:
This sounds like the same as #17473. The popup of the autocomplete is rendered inside a portal by default. You can either disable it or change the container to something else than the root element.
Hello together, thanks in advance for your support :)
Current Behavior 😯
when trying to use the Autocomplete component from Material UI, I face an issue with wrong position of the drop down while scrolling. The drop down has a fixed position and is not set under the text field of Autocomplete. The Autocomplete is used inside a web component. Do you have an idea, what it could be? Think nested scroll views are a big issue here. This behaviour seems to be for me as a bug. Issue is in chrome as well in firefox.
Expected Behavior 🤔
The position of the drop down from auto complete should remain if I scroll the "outer" ScrollView.
Steps to Reproduce 🕹
Steps:
The text was updated successfully, but these errors were encountered: