Edit and view modes need a readable visual split

What it is

One object has two full surfaces. View mode is a reading: body, outline, comments read-only. Edit mode is a bench: caret, formatting tools, fields that take focus. A glance has to split them: toolbar present or not, insertion caret in the body, “Editing” in the title region. This is the visual language of those two surfaces. Whether read and write collapse into one ambiguous record state is a CRUD-layer issue. Here the page (or block) is already two modes; the question is whether they still look like one thing. That a mode mark must sit where the eyes are is a more general human-factors result. Content products still have to draw the two chromes.

Why it happens

Viewing is for understanding; editing is for changing. The visual system uses toolbar density, a caret, and page margins to tell which job it is in. If both chromes share the same article look and only swap an “Edit” word in a corner, the split is absent while the eyes sit on the body: people alter a letter while reading, or treat writing as a preview. The split has to survive scroll: a sticky toolbar, a caret that follows focus, not a banner that flashed on entry. Color theme is not enough; color-blind and projected rooms lose that layer. Speech and screen-reader users need name and state, not only extra icons.

Studying it

The same document in “almost identical chrome” versus “no toolbar in view, full toolbar and caret in edit.” Alternate reading a passage and changing a word.

Independent variables: toolbar only in edit, a persistent Editing mark, caret at focus. Dependent variables: accidental edits while reading, treating edits as uncommitted preview, post-task “could I change that.”

Do not say “please enter edit.” Use goals: “change the due date to Friday” and “tell me what section 3 is about.” On a narrow screen, also watch whether the edit toolbar squeezes the body into something that still looks like reading—too much chrome can make the mode unreadable too.

Where it stops holding

Cell-level grid editing has cell chrome; the page can stay in view. A slideshow is a third mode and must not share the insertion caret with edit. A blank document being created has no finished reading, so edit-only is fine. High-contrast and dark themes still split by structure and control presence, not by a pale background alone.

Applying it

• View shows no format tools and no caret. After entering edit, the toolbar appears, the body shows a caret, and the title region keeps an Editing mark.
• Do not rely on a single color. Use presence of controls plus a text state that survives scroll.
• Leaving edit hides the toolbar and the caret so the surface no longer looks typeable.
• Verify: still frames of both modes, no pointer. People who did not design it mark which one can be changed. Wrong or guessed means the split failed. Then have someone read in view with hands on the keyboard and see whether any change lands.

Related

• Within the group: H8.09.2 The edit entry appears only when the person may edit · H8.09.3 Unexpected exit should keep a draft, not drop the work · H8.09.4 One person’s edit mode must not hijack others’ viewing
• Adjacent: H8.01 CRUD Operations · A10.02 Mode Errors · H8.08 Sharing Scope and Permission Settings
• Search terms: edit mode · view mode · authoring chrome