-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
When including a navbar dropdown in the "brand section", the dropdown is always open on mobile #1743
Comments
Yes you're right, but while we look for a solution you can control the behaviour of the mobile menu programmatically with the is-active prop. |
still same problem in 0.8.4 |
Hello @sugacube could you provide us an working example? Thanks. |
renders like |
i see. makes sense. i guess i'll have to report this with bulma then. |
Bug still exists with latests versions of bulma and buefy |
Overview of the problem
Buefy version: 0.8.3
Vuejs version: 2.6.10
OS/Browser: Windows - Firefox & Chrome
Description
If you create a navbar dropdown inside the "brand" section of the navbar, on mobile it is shown on top as expected, but fully open in stead of being able to close/open. Also the text is rendered next to the item in stead of in a popup.
Rationale
bulma / buefy navbar items automatically hide on tablet or mobile. If you have 1 or 2 small dropdown menus there is however still place on a mobile to show the menu's (tablets will fit even more).
It is a workaround with bulma in this case to put the dropdown inside the "brand" section, so these will always remain on top, even on mobile.
This works perfectly for normal navbar items.
Steps to reproduce
Expected behavior
On mobile screen, dropdown "Menu" shown on top of screen which can be clicked open/close and selected.
Actual behavior
On mobile screen, always open dropdown is shown with menu items rendered next to it.
Remark
I'm not sure this should be classified as a but or as a feature request. Please re-classify if you desire.
The text was updated successfully, but these errors were encountered: