Skip to content
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

User dropdown does not close anymore #3769

Closed
ksassnowski opened this issue Aug 31, 2022 · 3 comments
Closed

User dropdown does not close anymore #3769

ksassnowski opened this issue Aug 31, 2022 · 3 comments
Labels
bug Something isn't working unconfirmed

Comments

@ksassnowski
Copy link

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.

CleanShot 2022-08-31 at 07 31 43@2x

Expected behavior

The dropdown should be closed by default and it should be possible to close it again after opening it.

Steps to reproduce

  1. Install filament/filament:2.15.34 in a fresh application
  2. Log in with any user
  3. Notice that the user dropdown is already open and off to the side
  4. Clicking on the user avatar does not close the dropdown

Reproduction repository

https://github.com/ksassnowski/filament-user-dropdown-bug

Relevant log output

No response

@ksassnowski ksassnowski added bug Something isn't working unconfirmed labels Aug 31, 2022
@mohameedsherif
Copy link

Same issue here

@invaders-xx
Copy link
Contributor

invaders-xx commented Aug 31, 2022

There's a discussion opened on Discord and it's a known issue. For now, please revert back to 2.15.33 until issue solved by maintainers

@danharrin
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working unconfirmed
Projects
None yet
Development

No branches or pull requests

4 participants