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
The 2.15.34 release of Filament introduced a visual bug that causes the user menu dropdown in the admin panel to always be open. Clicking on the user avatar positions the dropdown correctly, but you're still unable to close it. This is probably related to #3443 but I haven't looked very deep into it. Version 2.15.33 does not contain this bug.
Expected behavior
The dropdown should be closed by default and it should be possible to close it again after opening it.
Steps to reproduce
Install filament/filament:2.15.34 in a fresh application
Log in with any user
Notice that the user dropdown is already open and off to the side
Clicking on the user avatar does not close the dropdown
We are very sorry for the inconvenience here. I just released a new version.
I pulled down PR #3443, checked it out locally, and it was all fine. Then for some reason it was broken when it got released. Maybe there was some cache in my dummy app that was still showing me the old version or something.
Should all be sorted now, we will investigate what happened.
Package
filament/filament
Package Version
v2.15.34
Laravel Version
v9.27.0
Livewire Version
No response
PHP Version
8.1
Problem description
The 2.15.34 release of Filament introduced a visual bug that causes the user menu dropdown in the admin panel to always be open. Clicking on the user avatar positions the dropdown correctly, but you're still unable to close it. This is probably related to #3443 but I haven't looked very deep into it. Version
2.15.33
does not contain this bug.Expected behavior
The dropdown should be closed by default and it should be possible to close it again after opening it.
Steps to reproduce
filament/filament:2.15.34
in a fresh applicationReproduction repository
https://github.com/ksassnowski/filament-user-dropdown-bug
Relevant log output
No response
The text was updated successfully, but these errors were encountered: