Loading…
Loading…
Dataset 20260827-2142-2f1b575 · measured 2026-08-27 21:42 UTC
The parser accepts the name, yet our rendering is byte-identical with and without the declaration while Chrome's is not. The declaration is being swallowed.
Each example is one declaration on a small page, drawn by Chrome and by our engine. Drag the handle to wipe between them.
min-height:20px✓pixel-exact
Our renderChrome8 pixels differ from Chrome, the largest by 64 of 255 on one channel.
min-height:calc(40% + 20px)✕parsed, no effect
Our renderChrome128 pixels differ from Chrome, the largest by 204 of 255 on one channel.
min-height:calc(20px + 4px)✓pixel-exact
Our renderChrome8 pixels differ from Chrome, the largest by 64 of 255 on one channel.
“Supported” on one example means “supported at the value we tried”. The property’s declared grammar has 8 branches; 2 of them carry a measurement. The publishing ceiling is 12 examples per property — a branch past it is left out by our choice, not by accident.
| Value | Measured |
|---|---|
| 20px | ✓pixel-exact |
| 50% | ✕parsed, no effect |
| min-content | not measured |
| max-content | not measured |
| stretch | not measured |
| fit-content | not measured |
| contain | not measured |
| auto | not measured |
Secondary evidence: 1 Web Platform Test carry a spec anchor pointing at this property. Only 1,254 tests in the whole corpus carry such an anchor, so an empty list here means nothing at all.
Measured against Chrome 148.0.7778.96 on 2026-08-27, with up to 40 candidate values tried per property. All properties · How the measurement works