demo · v140

Author Recipe

Now that the UA cascade is gone, the visual hierarchy is your job again. Switch between the old browser rule and three author recipes: flat rendering, explicit depth selectors, or container-aware fluid sizing.

Rendering recipe

Release notes hub

Chrome 140 migration guide

The same markup uses h1 for every sectioning root so the visual rule is easy to inspect.

Author CSS checklist

This nested article represents a page card, product note, or CMS block inside the main story.

which to pick

A is the cleanest answer if your markup is being audited anyway. B is closest to the legacy behaviour but burns the same author cycles you would spend demoting to h2. C plays best with the rest of the new layout primitives because it makes the rendered h1 size respond to the container instead of the markup depth alone.

see also