Simon Pieters in Elk: "The backstory here is- h1 was specifi..."

Here's the new 2025 reset.css:

h1 { margin-block: 0.67em; font-size: 2em; }

Thank you for adopting this on all your sites!

See https://github.com/whatwg/html/issues/7867

GitHub

Remove UA style for h1-h6 in section (et. al.) and hgroup · Issue #7867 · whatwg/html

If/when #7829 is merged, the following UA style doesn't make sense. Can it be removed? In the following CSS block, x is shorthand for the following selector: :is(article, aside, nav, section) @name...

The backstory here is

- h1 was specified to have automatic heading level based on the number of ancestor sections (or aside, article, nav).
- The default rendering was specified to (roughly) match, such that <section><h1> would have the same font-size and margin as h2
- cont...

January 16, 2025 at 4:37:59 PM

Web

- The default rendering was implemented in browsers, but not the heading level in the accessibility tree.
- Websites started to use sectioning elements, but didn't expect automatic heading levels. It was not possible for browsers to change that without breaking user expectations.

- The automatic heading level (a.k.a. the outline algorithm) was dropped from the spec, but the default UA stylesheet remained. This is what we're trying to remove now.