Skip to content

Dropdown with navmenu items using wire:navigate blocks UI after using the back button #2671

Description

@bsterckx

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:
Image

After clicking browser back button:
Image

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:dropdown position="bottom" align="end">
        <flux:button icon:trailing="chevron-down">dropdown</flux:button>

        <flux:navmenu>
            <flux:navmenu.item href="/settings" icon="user" wire:navigate>wire navigate link</flux:navmenu.item>
        </flux:navmenu>
    </flux:dropdown>

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)

  • I have provided easy and step-by-step instructions to reproduce the bug.
  • I have provided code samples as text and NOT images.
  • I understand my bug report will be closed if I haven't met the criteria above.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions