-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
Improve submenu behavior #4527
Comments
Hey @markdotto, Thanks for opening this issue! Unfortunately, it looks like it fails to pass the criteria neccessary for submitting to bootstrap. The following things are currently failing:
For a full list of issue filing guidelines, please refer to the bootstrap issue filing guidelines. thanks! |
follow the rulez son |
<3 |
Epic. :D |
How does this apply to the bootstrap submenu? Doesn't it use the 'sticky approach', because it stays open, or do you want to close it automatically? |
Hey @markdotto, Thanks for opening this issue! Unfortunately, it looks like it fails to pass the criteria neccessary for submitting to bootstrap. The following things are currently failing:
For a full list of issue filing guidelines, please refer to the bootstrap issue filing guidelines. thanks! |
This is a minor change to a minor release? :P |
@barryvdh I think you're referring to first-level menus in the navbar and buttons. Submenus being, for example, the child menu of a regular menu activated from the navbar. The first menu is sticky, but submenus are not. I personally find myself, coworkers and customers struggling from time to time with these as there's no time or space buffer, your focus is completely based on whether or not you're in the menu selection. |
After talking with @mdo, we're going to punt on this. Also, we'll be removing the flyouts in 3.0 \o/ more info to follow… |
Basically, this: http://thomaspark.me/2011/10/making-menus-escapable/
The text was updated successfully, but these errors were encountered: