You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use is-three-quarters, is-two-thirds, is-half, is-one-third, is-one-quarter classes, the total width of the container is the same.
But when I use is-1, is-2, is-3, is-4, is-5... the total width of the container is different even though the sum is 12.
For example:
is-2, is-4, is-6 or is-2 x 6 or is-3 x 4.
I checked in DevTool, and for example column with is-2 class has different width in two containers (197.89 px in one container and 189.99 px in another). is-3 has 288 px and is-6 has 582 px (or 605.67 px in another container). For example, widths of is-3 and is-6 or is-2 and is-4 are not proportional.
Expected behavior
The text was updated successfully, but these errors were encountered:
galacticjoel
changed the title
Different total widths when using is-1 - is-12 class
Different total widths when using is-1 - is-12 classes
Aug 1, 2024
This is about Bulma | the Docs.
Overview of the problem
This is about the Bulma CSS framework
I am not quite sure if this is an intended feature or a bug.
I'm using Bulma version [1.0.1]
My browser is: Brave
I am sure this issue is not a duplicate? No.
Description
Steps to Reproduce
My code:
Actual behavior
When I use is-three-quarters, is-two-thirds, is-half, is-one-third, is-one-quarter classes, the total width of the container is the same.
But when I use is-1, is-2, is-3, is-4, is-5... the total width of the container is different even though the sum is 12.
For example:
is-2, is-4, is-6 or is-2 x 6 or is-3 x 4.
I checked in DevTool, and for example column with is-2 class has different width in two containers (197.89 px in one container and 189.99 px in another). is-3 has 288 px and is-6 has 582 px (or 605.67 px in another container). For example, widths of is-3 and is-6 or is-2 and is-4 are not proportional.
Expected behavior
The text was updated successfully, but these errors were encountered: