Remove parent block selector while in Write mode

[richtabor]

Brief

The current implementation of the parent block selector in Write mode disrupts the editing paradigm, as selecting the parent block leads to editing design-level (the parent <main> group block in a template or the post/content block otherwise.

Write mode is designed to simplify content input and prioritize content-focused interactions, but editing the top-most parent block while in this mode breaks this intended separation between writing and design.

Additionally, the parent block selector becomes less useful in Write mode for patterns. Write mode already flattens patterns, allowing easier selection and interaction, making the parent block selector nearly redundant in this context.

Steps to Reproduce

1. Enter Write mode.
2. Select text in a pattern.
3. Select the parent block selector to select the current pattern.
4. Select the parent block selector again to select the block surrounding all patterns.
5. Now you're at the top-level container group, or the post/content block—no longer editing content.

Expected Behavior

In Write mode, the focus remains on writing and direct interaction with patterns and their content blocks only.

Actual Behavior

Selecting a top-most parent block shifts the interaction toward design-oriented edits, misaligning with the Write mode’s purpose.

Visual

Note how using the parent block selector gets you to the Post Content block, which is not within the Write mode conditions, allowing design tooling while in Write mode. Also note how selecting the pattern in Write mode is as effective—if not more—than using the parent block selector.

CleanShot.2024-11-01.at.13.24.35.mp4