Miroslav.V

Another update. We have scheduled responsive paddings, margins and min-height to v.1.5.0. It will be release after the WP 7.0 drops.

Hello @sunny,

Good timing: we have actually added an option to disable this link in upcoming update 🙂 Will be released in a day or two. It will live in Settings > Better Block Editor, “Features” tab.

Just a quick follow-up. We have discussed it internally and our art director expressed the same concerns as you did. So we will be implementing responsiveness for margins and paddings in one of closest upcoming updates.

Thanks for your feedback – it helped finding the issue early.

An off-topic. Now as I read my comment, I realise it sounds somewhat defensive. That was not the intention. I was just excited to share the thought process that went into creating BBE 🙂

Your feedback regarding the usability of the Visibility panel is noted, and we will discuss it with the team.

Cheers!

• This reply was modified 2 months, 3 weeks ago by Miroslav.V.

Most of the controls are intuitive with the exception of the visibility settings. Why not follow the common pattern where we simply have “Hide” toggles for mobile, tablet, desktop? This would also fix the problem of un-hiding blocks with display:flex; which is what is causing this reported issue.

This is a good question.

Note that my answer will be very subjective (as I’m the product designer). I may be wrong. So take it with a grain of salt. But it boils down to two consideration:

1. UI/UX consistency. You’ve noticed that unlike conventional page builders we do not have multiple settings for multiple breakpoints. You only choose one breakpoint per block and change settings at that breakpoint. Allowing to change visibility at multiple breakpoints will break this consistency.
2. Editor performance. If you ever wondered why (for example) Elementor gets slower when your have more elements on the page, that’s the reason why: each additional breakpoint creates a dedicated set of controls. The more of those controls you have, the more hardware resources the editor consumes. And consequently slower it becomes.

Our goal was to give Block Editor users only the necessary controls without altering the editor too much. Those decisions were made based on our two decades of building themes, plugins and websites with WordPress. So this is the classical example of 99 “no” to every 1 “yes”.

I’m not trying to convince that our approach is right. Only stating the fact that BBE reflects our experience. And experience is very different for different people.

We understand that we cannot please everyone with decisions we made. So our best hope is some part of the WP community will find our work useful.

Now to the issue you’ve pointed out. You can expect a bugfix within 24h.

Hi,
Quick update. That was a “technical debt” on our side.
We’re currently testing a version without the .wpbbe-ref-anchor elements, and the update should be out in a day or two.