mava0

That’s good news, thank you.

Is there any link or page I can expect the Alpha to be released on?

There’s no second option for adding the download attribute?

Thanks for your response,

Although this topic wasn’t answered, the main question was answered in another topic. It was all connected to the integration of the GuBe tablet/mobile previewer in the GB plugin.

The problem is still persistent, also images inside of the grid don’t resize with the previewer.

It works fine in live and in ‘preview page in new tab’, but not in the editor itself.

Ok I see.

thank you.

Just as a heads up, are you aware of the vendor differences in the use of flexbox? Maybe important to consider?

Quote from css-tricks.com

Prefixing Flexbox
Flexbox requires some vendor prefixing to support the most browsers possible. It doesn’t just include prepending properties with the vendor prefix, but there are actually entirely different property and value names. This is because the Flexbox spec has changed over time, creating an “old”, “tweener”, and “new” versions.

Perhaps the best way to handle this is to write in the new (and final) syntax and run your CSS through Autoprefixer, which handles the fallbacks very well.

Alternatively, here’s a Sass @mixin to help with some of the prefixing, which also gives you an idea of what kind of things need to be done:

@mixin flexbox() {
  display: -webkit-box;
  display: -moz-box;
  display: -ms-flexbox;
  display: -webkit-flex;
  display: flex;
}

@mixin flex($values) {
  -webkit-box-flex: $values;
  -moz-box-flex:  $values;
  -webkit-flex:  $values;
  -ms-flex:  $values;
  flex:  $values;
}

@mixin order($val) {
  -webkit-box-ordinal-group: $val;  
  -moz-box-ordinal-group: $val;     
  -ms-flex-order: $val;     
  -webkit-order: $val;  
  order: $val;
}

.wrapper {
  @include flexbox();
}

.item {
  @include flex(1 200px);
  @include order(2);
}

FYI, the reason it worked with Kadence is because it just blatantly overrode the setting I made in the Block Builder by assigning it’s margins on every hx element globally:

.single-content h1, .single-content h2,
.single-content h3, .single-content h4,
.single-content h5, .single-content h6 {
    margin: 1.5em 0 .5em;
}

By this it balanced them all out … a little cheaky though.

• This reply was modified 5 years, 8 months ago by mava0.

This is the page running the free GP theme:

https://badrsolutions.com/IGCSE/page-with-generateblocks/

I can change the theme to others if needed.

• This reply was modified 5 years, 8 months ago by mava0.

Things are changing rapidly in the block editor, and once something is added to a theme it has to stay there for backward-compatibility purposes.

I see your point.

it’s a new feature that not a lot of people have taken advantage of.

I’m not sure if you meant people as in users, or people as in developers. As for users then you must be more informed about that then me, as for developers, then even some devs of free Block Editor plugins have integrated the feature into their blocks: Stackable, Otter and Kadence. With respectively 30.000, 60.000 and 80.000 active installs.