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
Add options to the <Select> component, then click on it to open the menu.
When menu is opend then try scroll page.
Current behavior 😯
The steps outline the usage of the Material-UI <Select> component. After adding options to the <Select>, clicking on it will trigger the opening of the dropdown menu. However, a potential issue arises where scrolling on the page becomes disabled.`
Expected behavior 🤔
An alternative approach is to consider using the Autocomplete component, which currently functions as expected in this scenario. The same behavior could potentially be applied to the <Select> component for its menu options.
Context 🔦
Consider a scenario where a <Select> component is incorporated into a form situated in the upper section of a page, and additional information resides in the lower portion, beyond the initial view. As the user interacts with the <Select>, they simultaneously wish to scroll down to view more details that influence their selection. However, when the user clicks on the <Select>, an unexpected limitation arises – the page becomes unresponsive to scrolling. Consequently, the user is compelled to close the <Select>, scroll down to the desired section, then scroll back up to resume their selection process. This interruption in the scrolling behavior creates a less fluid and seamless user experience, potentially leading to frustration and a disruption in the natural flow of form completion.
Your environment 🌎
No response
The text was updated successfully, but these errors were encountered:
Duplicates
Latest version
Steps to reproduce 🕹
Steps:
<Select>
i.e.@mui/material/Select
<Select>
component, then click on it to open the menu.Current behavior 😯
The steps outline the usage of the Material-UI
<Select>
component. After adding options to the<Select>
, clicking on it will trigger the opening of the dropdown menu. However, a potential issue arises where scrolling on the page becomes disabled.`Expected behavior 🤔
An alternative approach is to consider using the
Autocomplete
component, which currently functions as expected in this scenario. The same behavior could potentially be applied to the<Select>
component for its menu options.Context 🔦
Consider a scenario where a
<Select>
component is incorporated into a form situated in the upper section of a page, and additional information resides in the lower portion, beyond the initial view. As the user interacts with the<Select>
, they simultaneously wish to scroll down to view more details that influence their selection. However, when the user clicks on the<Select>
, an unexpected limitation arises – the page becomes unresponsive to scrolling. Consequently, the user is compelled to close the<Select>
, scroll down to the desired section, then scroll back up to resume their selection process. This interruption in the scrolling behavior creates a less fluid and seamless user experience, potentially leading to frustration and a disruption in the natural flow of form completion.Your environment 🌎
No response
The text was updated successfully, but these errors were encountered: