This is about the Docs.
Inconsistent use of navbar-burger in the site itself, versus examples shown.
This is about the Bulma Docs
I'm using Bulma version 0.6.1
The navbar documentation says that the navbar burger should be
<button class="button navbar-burger">
However, Bulma's own site has a number of instances of div or span with
class="navbar-burger burger"
The second class (.burger) doesn't appear in the CSS at all, as far as I can see.
The site is a very useful working reference of Bulma in action, so it would be good to be accurate. Should the burger class be there, or is it an error?
It also seems that the documentation shouldn't use a This is what have been working for me. Thanks, the div works well here too. Yup, it's supposed to be a div based on the working examples being divs and my own experimentation. I addressed this is a PR over here that hopefully will get included in the next release! Cool - that's one half. The other half is the bulma.io site which uses I believe that the https://github.com/jgthms/bulma/blob/fdeba5d111f8a7e695de4fc7a70966348daeeb03/docs/_javascript/main.js#L43-L56 The navbar example in the documentation uses Therefore, the only relevant class for Bulma is Ah thanks - I had checked through css/bulma.css, but not through the javascript From the point of view of analysing a site, it would be nice if all the bulma css classes had some common prefix so you could recognise them as belonging to bulma. But from another point of view, it would be a lot of extra typing. If you are using JQuery try this With the following HTML (Using https://fontawesome.com/ like Hope it'll help :smile: Also, when I follow the example on the site, I can get the burger menu to collapse and open, but _unlike_ on the website, I can't get the menu bar to display when the page is wide. That is, I get the burger menu, and _only_ the burger menu also on the desktop. Sigh... I am on the hero docs btw. This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.~
$ egrep -R "class.*[^-]burger" .
./docs/_includes/examples/navbar-bottom.html:
All 9 comments
button, it will look more like a button than navbar-item that it shows in the results of the documentation. It should be using something like<div class="navbar-burger">
<span></span>
<span></span>
<span></span>
</div>
class="burger" in addition to class="navbar-burger"burger class in that element is not related to Bulma itself. If you run git grep "\.burger" you'll see that it is being used from JavaScript:.navbar-burger (which is a class in Bulma) as the selector to toggle the navbar. I think the documentation site uses .burger to avoid collisions with the examples..navbar-burger; it is up to you if you decide to use this class as the selector for toggling the navbar from JavaScript or use another, like .burger.~
docs/_javascript/main.js: const $burgers = getAll('.burger');
~ // Close mobile & tablet menu on item click
$('.navbar-item').each(function(e) {
$(this).click(function(){
if($('#navbar-burger-id').hasClass('is-active')){
$('#navbar-burger-id').removeClass('is-active');
$('#navbar-menu-id').removeClass('is-active');
}
});
});
// Open or Close mobile & tablet menu
$('#navbar-burger-id').click(function () {
if($('#navbar-burger-id').hasClass('is-active')){
$('#navbar-burger-id').removeClass('is-active');
$('#navbar-menu-id').removeClass('is-active');
}else {
$('#navbar-burger-id').addClass('is-active');
$('#navbar-menu-id').addClass('is-active');
}
});
<i class="fa [...]) <nav id="navMenu" class="navbar is-fixed-top" role="navigation" aria-label="main navigation">
<div class="container">
<div class="navbar-brand">
<a class="navbar-item" href="#"><i class="fas fa-home fa-lg"></i></a>
<a class="navbar-item is-hidden-desktop" href="#where-hours"><i class="far fa-clock fa-lg"></i></a>
<div id="navbar-burger-id" class="navbar-burger">
<span></span>
<span></span>
<span></span>
</div>
</div>
<div id="navbar-menu-id" class="navbar-menu">
<div class="navbar-start">
<a class="navbar-item" href="#section-1">First Section</a>
<a class="navbar-item" href="#section-2">Second Section</a>
<a class="navbar-item" href="#section-3">Third Section</a>
</div>
<div class="navbar-end">
<a class="navbar-item is-hidden-touch" href="#where-section"><i class="far fa-clock fa-lg"></i></a>
</div>
</div>
</div>
</nav>
Peace
Most helpful comment
It also seems that the documentation shouldn't use a
button, it will look more like a button thannavbar-itemthat it shows in the results of the documentation. It should be using something likeThis is what have been working for me.