This is about Bulma.
Is it a bug/feature/question or do you need help?
BUG
This is about the Bulma CSS framework
I'm using Bulma version [0.7.1]
My browser is: Chrome
I'm trying to use a container with .container .is-fluid classes. The docs it says that it will keep a 32px gap in both sides on any viewport size. I read that the $gap variable was changed to 64px recently, but that's not my problem. My problem is that once the viewport hits below1088px, the gap on both ends disappear. I wonder if this is part of a bigger bug?
Create an index.html file and copy and paste the following:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<title>Page Title</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" media="screen" href="https://cdnjs.cloudflare.com/ajax/libs/bulma/0.7.1/css/bulma.css" />
</head>
<body>
<section>
<div class="container is-fluid">
<div class="notification">
This container is <strong>fluid</strong>: it will have a 32px gap on either side, on any viewport size.
</div>
</div>
</section>
</body>
</html>
Open the the index.html in a browser and resize window manually
The nav bar should keep its margins on each size
The nav bar goes full width:

Wanted to follow up on this. This seems to be a legitimate issue, but I don't really know. Any insight would be awesome. Thanks!
It seems to be a documentation issue. The gap should only appear on $desktop viewports and onwards.
Any plans to introduce a new class to restore this functionality? I'm not really that on board with having no spacing for container on mobile.
@jgthms Thanks. To @nojaf point, is there a way to keep the gap on viewports lower than $desktop ?
I believe a is-fluid-mobile additional class could exist.
For mobile spacing, I'd say using a .section is preferred though.
@jgthms I don't believe is-fluid-mobile is a thing.
I just found this issue as is-fluid was not behaving as the documentation states. The expected behaviour (spacing on mobile screen sizes) would be desirable in a class.
I believe a
is-fluid-mobileadditional class could exist.For mobile spacing, I'd say using a
.sectionis preferred though.
I was about to plus-1 this until I saw @jgthms's comment about .section, which I now think is a good solution.
The .container page in the docs is indeed misleading however: "...will have a 32px gap on either side, on any viewport size."
The .container page in the docs is indeed misleading however: "...will have a 32px gap on either side, on any viewport size."
I am curious as to why the docs is still midleading if .section is to be used for mobile.
I would like to agree with @vgm106. If the documentation is wrong:
a) why has this not been rectified yet? I do not mind to do it but I'd like to be certain this is accurate.
b) why does the example in the documentation behave as described in the documentation?
I'm only starting out with Bulma so apologies if my concerns aren't valid.
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.
Not sure .section is the the best out-of-box solution for navbar as it introduces a 3rem of top bottom padding. Fixes the left/right padding though...
Most helpful comment
I believe a
is-fluid-mobileadditional class could exist.For mobile spacing, I'd say using a
.sectionis preferred though.