← back to v136 · deprecate-special-font-size-rules-for-h1-within-some-elements
conformance · v136
v136 · deprecate-special-font-size-rules-for-h1-within-some-elements — conformance probe
5 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
bare-h1-default-font-size |
A bare top-level <h1> still renders at the user-agent default font size (the deprecation only targets nested cases). spec ↗ | script | … | |
h1-in-section-uses-base-h1-size |
Per the new spec, an <h1> nested in <section> no longer gets a downsized UA style — it matches a bare <h1>. spec ↗ | script | … | |
h1-in-article-uses-base-h1-size |
An <h1> nested in <article> matches the bare <h1> font size under the new spec. spec ↗ | script | … | |
h1-in-aside-uses-base-h1-size |
An <h1> nested in <aside> matches the bare <h1> font size under the new spec. spec ↗ | script | … | |
h1-in-nav-uses-base-h1-size |
An <h1> nested in <nav> matches the bare <h1> font size under the new spec. spec ↗ | script | … |