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
When the Escape key is pressed, the Dialog is closed first and the Alert is still displayed.
Expected behavior
Not sure what behavior should be enabled by default. Was expecting the layers to be closed in the order the user opened them (Toast on the first Escape key press, then the Modal on the second press). Ideally, we'd like to see a quick and easy way to configure this behavior.
Context
I am trying to implement a feature for a common use case in a production-facing React application. There are 50+ pages where a user can have both MUI Alerts and Dialogs open simultaneously. We need a solution that doesn't cause components that use Dialogs to be dependent on the open state of Snackbar or Alert components. We have been searching the MUI documentation and StackOverflow for this particular use case, but it has not come up in searches.
Steps to reproduce
Steps:
Current behavior
When the Escape key is pressed, the
Dialog
is closed first and theAlert
is still displayed.Expected behavior
Not sure what behavior should be enabled by default. Was expecting the layers to be closed in the order the user opened them (Toast on the first Escape key press, then the Modal on the second press). Ideally, we'd like to see a quick and easy way to configure this behavior.
Context
I am trying to implement a feature for a common use case in a production-facing React application. There are 50+ pages where a user can have both MUI
Alert
s andDialog
s open simultaneously. We need a solution that doesn't cause components that useDialog
s to be dependent on the open state ofSnackbar
orAlert
components. We have been searching the MUI documentation and StackOverflow for this particular use case, but it has not come up in searches.Your environment
npx @mui/envinfo
Search keywords: Dialog Snackbar Alert Escape
The text was updated successfully, but these errors were encountered: