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
Steps to reproduce:
When a user wire:navigates to another page via a link rendered via the navmenu within a dropdown and then clicks the browser's back button, leftover classes block future page interaction. (issue is not there when using menu instead of navmenu). This looks like the same issue as described in #2323 but this time with the navmenu items.
Initial page:
After clicking browser back button:
Code snippets to replicate the problem
Installed a new laravel app with the livewire stack.
Added a simple dropdown with navmenu item using wire:navigate to the dashboard page.
Click on this navmenu item and then press back.
Flux version
v2.15.0
Livewire version
v4.3.3
Tailwind version
v4.3.2
Browser and Operating System
Chrome on Windows 11
What is the problem?
Steps to reproduce:
When a user wire:navigates to another page via a link rendered via the navmenu within a dropdown and then clicks the browser's back button, leftover classes block future page interaction. (issue is not there when using menu instead of navmenu). This looks like the same issue as described in #2323 but this time with the navmenu items.
Initial page:

After clicking browser back button:

Code snippets to replicate the problem
Installed a new laravel app with the livewire stack.
Added a simple dropdown with navmenu item using wire:navigate to the dashboard page.
Click on this navmenu item and then press back.
Screenshots/ screen recordings of the problem
Example of the process. Notice the UI gets blocked after pressing the back button:
recording.mp4
How do you expect it to work?
When clicking the back button, a user should still be able to interact with the page
Please confirm (incomplete submissions will not be addressed)