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

Mobile menu will not remain open if click inside Google chrome dev console #57603

Open
bradhogan opened this issue Jan 5, 2024 · 3 comments
Open
Labels
[Block] Navigation Affects the Navigation Block Browser Issues Issues or PRs that are related to browser specific problems [Feature] Interactivity API API to add frontend interactivity to blocks. [Type] Enhancement A suggestion for improvement.

Comments

@bradhogan
Copy link

Description

Hey there. I thought this was initially a Gutenberg issue, but appears to happen without Gutenberg active as well (so ignore that part in my video).

(initially reported in wp trac here).

Step-by-step reproduction instructions

Video showing issue here: https://soapbox.wistia.com/videos/myXwb0ApbR

Screenshots, screen recording, code snippet

No response

Environment info

  • wp 6.4.2
  • gutenberg 17.4.1
  • chrome
  • mac sonoma

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

@bradhogan bradhogan added the [Type] Bug An existing feature does not function as intended label Jan 5, 2024
@krokodok
Copy link
Contributor

krokodok commented Jan 5, 2024

I researched this issue a little when it was reported on Trac earlier and there was some discussion if this is a bug or preferred behaviour: #55198 (comment)

@bradhogan
Copy link
Author

@krokodok Definitely not preferred behavior. Works properly in Safari and FF. You should be able to use the dev console to view and make changes to the mobile menu when open.

@krokodok
Copy link
Contributor

krokodok commented Jan 5, 2024

Here is a comment how you should be able to debug these elements anyway: #56094 (comment)

Whether this behaviour is standardized, I don't know. I also feel that it would have more benefits not closing the elements when interacting with something else than the website itself. Every website seems to do it differently, so it's hard to find a consensus. Interestingly, the user profile menu on Google's home search page functions exactly in the same way as the new WordPress menu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Navigation Affects the Navigation Block Browser Issues Issues or PRs that are related to browser specific problems [Feature] Interactivity API API to add frontend interactivity to blocks. [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

6 participants