Locking a Block and Block Outlines

[mtias]

Not sure about this, but as part of reducing the visual weight in nested contexts, I think we should not render most of the UI on locked templates. For example, if we have a wrapper block, with some column blocks inside, and the wrapper is set to be locked, we should avoid rendering individual column outlines, or fade the outline further.

[karmatosed]

I would +1 to fading the outline. I also am very aware nesting rapidly becomes quite a concentrated heavy interface.

[kraftner]

But what if that wrapper block needs to be selectable because even though it is locked it has some attributes that have Inspector Controls?

[ZebulanStanphill]

@kraftner I wonder if this is a situation where block breadcrumbs in the sidebar might be useful. See this comment on #6459.

[kjellr]

👋 Block outlines have changed a bit since this issue was filed, and will likely change more if #14961 makes it in. In the meantime, I'm having a little trouble understanding the nature of this issue. I think a couple more examples (ideally visual ones, even if they're messy!) would help explain the concept here a little more clearly. Thanks!

[mtias]

@kjellr this is about using blocks to define structure, but preventing its UI (selection state, outlines, toolbar, etc) from showing up. Imagine the current "post content" as a container block that has no interface — it just transparently contains all the blocks.

[chrisvanpatten]

I would actually say this is even more valuable if #14961 gets merged, because it gives container blocks an even greater visual weight/visibility. The changes in #14961 make a lot of sense if visualising the container itself is important, but in some cases the container itself is more of an implementation detail which should be invisible.

[karmatosed]

Linking this one to the exploration work going on here: #18667

[ZebulanStanphill]

#18105 removed the dashed parent/child block outlines and padding, so I'm closing this issue since it is now irrelevant.