Loading…
Loading…
Dataset 20261011-0550-f160c57 · measured 2026-10-11 05:50 UTC
Some of the examples match Chrome and some do not. The count beside the verdict says how many — 11 of 12 — and the values that differ are listed on the property page. It is neither a pass nor a failure, and filing it under either would be a lie in one direction.
Here: 4 of 5 examples match Chrome. The one that does not: overflow:visible — shown first below, each with its difference map.
5 examples, 4 of them matching Chrome, the rest first. Each is one declaration on a small page, drawn by Chrome and by our engine. Drag the handle to wipe between them.
overflow:visible✕renders differently
Our renderChrome798 pixels differ from Chrome, the largest by 52 of 255 on one channel.
overflow:hidden✓pixel-exact
Our renderChromeIdentical to Chrome: nothing differs, so there is no difference map to show.
overflow:clip✓pixel-exact
Our renderChromeIdentical to Chrome: nothing differs, so there is no difference map to show.
overflow:scroll✓pixel-exact
Our renderChromeIdentical to Chrome: nothing differs, so there is no difference map to show.
overflow:auto✓pixel-exact
Our renderChromeIdentical to Chrome: nothing differs, so there is no difference map to show.
“Supported” on one example means “supported at the value we tried”. The property’s declared grammar has 5 branches; 5 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 |
|---|---|
| hidden | ✓pixel-exact |
| clip | ✓pixel-exact |
| scroll | ✓pixel-exact |
| visible | ✕renders differently |
| auto | ✓pixel-exact |
Secondary evidence: 24 Web Platform Tests 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.
+ 12 more
Measured against Chrome 148.0.7778.96 on 2026-10-11, with up to 40 candidate values tried per property. All properties · How the measurement works