Hi …
I also have that problem. And also have the problem when the padding is set for example to 50 px. Always between each bloc … only see on internet explorer …also at the Blocsapp homepage …a few days / weeks ago a send a bug @Norm
any solution for this with the Internet explorer ?
tom
update: when I for example put a heading inside there is no padding bug ( watch on safari )
still there problem with the internet explorer … with content or without content …
update1: I often use a bloc and set a background image …set a class and a hight ( for example 500 px ) and use no text inside … than I also have a padding bug …set the padding to 20px but still the same …
@MDS Thank you MDS. You choose to solve the problem with a “img-margin-top” custom class.
It worked well in the Blocs 2 before, without custom class.
@Norm I still think so this is a bug. Why I need to use custom class when I selected the padding is none.
Whenever I insert an image and the padding is none there is a white line.
(If the image is very narrow the white line appear top and bottom too.)
So doesn’t fit.
Yeah it’s a bug. But it comes from bootstrap 4 and it’s use of flexbox. Some elements in bootstrap create the extra padding below when they use display classes for layout. Try left aligning the image and the space will go away. The centering class from bootstrap that is applied to images by default also causes the white space. I found a bunch of scenarios that cause this on no padding Blocs all caused by the bootstrap layout classes.
Also, this is just my opinion but using an entire bloc just to add a divider is wasteful, that’s extra code bloat the browser reads that could be added with a class to apply a border on the lower bloc edge.
I’m working on a bunch of these issues right now so I’ll try to come up with a solution that doesn’t break other areas.
An example @Norm would be fonts. The sheets are applied site wide. It would be better to be page specific if possible. No need loading google fonts on pages that don’t call for them.
I’ve tracked the cause down, it looks like its the main Bloc container. I’ve fixed it but Im unsure as to whether it has broken anything else as it’s a class that the foundation of pages are built on.
I’ll keep testing and see if its suitable for inclusion in 3.1 build 6.