SwipeableDrawer: transition equal to 0 hangs application

[iliubinskii]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Steps to reproduce 🕹

Link to live example:
Not working right

Steps:

1. Click button
2. Close drawer
3. Try to click button again

Current behavior 😯

At step 3 button is not clickable. App is "hanging"

Expected behavior 🤔

At step 3 button should be clickable

Context 🔦

No response

Your environment 🌎

npx @mui/envinfo

  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

[DIWAKARKASHYAP]

Hi , @ilyub
i check your example and also check the official doc of MUI . then i find that you miss an argument inside the object in line number 43 in your code that is " exit: 0 "

after write this argument , your code working properly
and you have another option , in line no 43 you can replace the whole object by the time in millisecond

[iliubinskii]

check your example and also check the official doc of MUI . then i find that you miss an argument inside the object in line number 43 in your code that is " exit: 0 "

In fact I didn't miss "exit" argument. I wanted to remove entering transition, while leaving default duration for exit transition.

To me, the most logical behavior is to use default for missing arguments. I think this should be very easy to do.

If you can't fix component hanging with missing exit, then you might make it required.

In any case, current situation when you let me skip "exit" and it hangs component is buggy.

[DIWAKARKASHYAP]

got it . i try to fix this

[mnajdova]

As a workaround you can use exit theme.transitions.duration.leavingScreen. I feel like changing the logic at this moment could be considered a breaking change. In v6 we can consider using the best defaults if they are not specified.