-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - Using Tabs inside Modal breaks UI #4805
Comments
I couldn't reproduce the issue. Please share a sandbox. issue4805.webm |
I also got the same error |
I also got the same problem. Changing to the second tab and closing the modal make other elements unclickable. I noticed that the div opened for the modal in the react portal stays there even if the modal is closed. |
Here is a reproduction of the issue Fresh demo with react-router-v7, of course the UI is broken because of tailwind 4, but that's another issue. In our app, we are still on tailwind 3, the bug with Modal was found when upgrading from Remix 2 to react-router-v7. Video : Enregistrement.de.l.ecran.2025-02-11.133922.mp4 |
I'm having the same problem and I think the internal components should be cleared after the Model is closed. |
HeroUI Version
2.6.14
Describe the bug
When a Modal containing Tabs is closed after switching between tabs, the modal's content remains visually present on the screen but in a "ghosted" state. This creates a UI layer that appears invisible but still occupies space and interferes with user interactions, as clicks are being intercepted by the invisible modal content.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Reproducible steps:
Expected behavior
When the modal is closed, all of its content, including any tab components and their associated content, should be completely removed from both the DOM and visual layer. There should be no residual UI elements or invisible interactive areas remaining after the modal is closed.
Screenshots or Videos
No response
Operating System Version
macOS
Browser
Chrome
The text was updated successfully, but these errors were encountered: