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 using an Android phone (or Chrome device toolbar and selecting a mobile device) to access the demo or any other page where you use a bottom sheet, the below happens when you follow these steps:
You click the button to open the bottom sheet
You close the bottom sheet
You click the button again
If you close the bottom sheet by dragging on the body or by tapping outside (in case the bottom sheet doesn't cover the whole screen), the above works fine.
However, if you close the bottom sheet by dragging exactly on the header, then tapping the button again doesn't work. You need to tap twice in order to open the bottom sheet again. In fact, the first tap is not registered no matter where you tap on the screen (other buttons etc.)
After some experimenting, we found that adding the below to our css:
solves the problem, by removing the "pan-x" option that is set. Don't know if this is the correct solution or maybe it creates other problems that we don't see.
The text was updated successfully, but these errors were encountered:
When using an Android phone (or Chrome device toolbar and selecting a mobile device) to access the demo or any other page where you use a bottom sheet, the below happens when you follow these steps:
If you close the bottom sheet by dragging on the body or by tapping outside (in case the bottom sheet doesn't cover the whole screen), the above works fine.
However, if you close the bottom sheet by dragging exactly on the header, then tapping the button again doesn't work. You need to tap twice in order to open the bottom sheet again. In fact, the first tap is not registered no matter where you tap on the screen (other buttons etc.)
After some experimenting, we found that adding the below to our css:
.bottom-sheet__draggable-area {
touch-action: unset !important;
}
solves the problem, by removing the "pan-x" option that is set. Don't know if this is the correct solution or maybe it creates other problems that we don't see.
The text was updated successfully, but these errors were encountered: