Too many dividers make the surface look shattered

What it is

Every divider is a forced pause. When pauses are as dense as rows, the page is no longer a few blocks; it is a stack of shredded strips. Divider fragmentation stops the scan from forming large groups: the eye hops along lines, and the rhythm of the content is replaced by the rhythm of the lines. The failure is not one line in the wrong place. It is line density already higher than the structure needs.

Why it happens

Pauses have a budget. An occasional line can mark a class change; a line on every row makes every pause equally loud, and the class change can no longer be heard. Gridness rises, objectness falls: people start counting cells instead of reading groups. Fragmentation also stacks with scroll — each line flashes as it enters the viewport, and a long list becomes a fence. If only one row of content sits between lines, content is demoted to filler and visual weight lands on the lines. Card strokes, list row lines, and block rules on one screen are three cutting systems fighting, and which one expresses the real structure becomes unreadable. Cutting lines is not “prettier.” It returns the pause budget to real boundaries.

Studying it

Present the same content with no row lines, lines only between groups, and a line on every item, on scan and grouping tasks, plus a “shattered / whole” description. Independent variables: line density, whether card strokes are also present. Dependent variables: grouping time, number of large groups correctly reported, eye-tracking dwell on lines. A line on every item should move dwell from content onto lines, and large groups should be reported as “many small ones.”

Where it stops holding

A data table may need row lines or zebra striping to track a row across columns; that is tracking, not class cutting, and density can be higher. High-contrast modes and some accessibility themes strengthen hairlines, so a density that was fine becomes shattered and must be checked there. Print has no scroll flash and can tolerate the same density better than a screen.

Applying it

• Treat lines as a pause budget: about as many lines as there are real class boundaries on one screen.
• Prefer spacing and section headers in lists, not lines between rows.
• When a card plate or a block fill already exists, drop the duplicate line.
• How to check: shrink to a thumbnail. You should still see three to five blocks, not a fence. A screen of horizontal rules is already shattered.

Related

• Within the group: E4.20.1 A divider is a forced cut for when the relationship would otherwise be unclear · E4.20.2 Whitespace groups by spacing, without drawing an edge · E4.20.4 Too little whitespace makes separate items read as one group
• Adjacent: E4.03 Tables · E4.01 Cards
• Search terms: visual noise · fragmentation · divider density