4 ms·
> Sub menus are really hard to do right on a mobile device No, they are not. Bootstrap is too opinionated here by not supporting nested menus. There are plenty
by Eduard 6y ago
> Sub menus are really hard to do right on a mobile device
No, they are not. Bootstrap is too opinionated here by not supporting nested menus. There are plenty of use cases for them, a navigable sitemap or your common application toolbar for example.
And accessibility is also a non-issue, see W3C's / WCAG's recommendations: https://www.w3.org/TR/wai-aria-practices/#menu https://www.w3.org/TR/wai-aria-practices/#menu
Speaking of accessibility: I'm surprised that Bootstrap only cares little about this important topic, especially considering implementing it on websites is required by law in many countries.
- hombre_fatal 6y agoI mean, submenus are difficult. Even single-element tooltips are complicated enough to warrant a dedicated library that Bootstrap uses: https://popper.js.org/ https://popper.js.org/ Nested menus are no easier to make generic. Or they can easily be too opinionated for the Bootstrap team's tastes. Also I don't think dropping something from your API makes you more opinionated. Their solution would be opinionated by definition if they had one. Nothing stops you from building your own or anybody from building a library that solves the problem. If you think it's easy, then you sound like the right person to take on the challenge.
- Eduard 6y agoCiting mdo, https://github.com/twbs/bootstrap/pull/6342#issuecomment-11594010 https://github.com/twbs/bootstrap/pull/6342#issuecomment-115... : "We haven't seen anyone using submenus in meaningful ways and the code necessary to make them work well is just too much overhead. Submenus just don't have much of a place on the web right now, especially the mobile web." This is very opinionated.
- gjvc 6y ago> No, they are not. Bootstrap is too opinionated here by not supporting nested menus Agree 10x