← back to v155 · closest-corner-and-farthest-corner-radii-for-circle-and-ellipse-basic-shapes
conformance · v155
v155 · closest-corner-and-farthest-corner-radii-for-circle-and-ellipse-basic-shapes — conformance probe
8 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
8
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
circle-accepts-closest-corner |
circle() accepts the closest-corner radius keyword. spec ↗ | script | … | |
circle-accepts-farthest-corner |
circle() accepts the farthest-corner radius keyword. spec ↗ | script | … | |
ellipse-accepts-corner-keywords |
ellipse() takes two radii, and both accept the corner keywords. spec ↗ | script | … | |
side-keywords-still-accepted |
The pre-existing closest-side and farthest-side keywords must keep working: this is an addition, not a replacement. spec ↗ | script | … | |
corner-keywords-work-in-shape-outside |
The keywords work in shape-outside, not only clip-path. spec ↗ | script | … | |
corner-keywords-work-in-offset-path |
The keywords work in offset-path, completing the set of properties that take a basic shape. spec ↗ | script | … | |
radial-gradient-has-always-accepted-them |
radial-gradient accepted these keywords long before shapes did. This is the parity being fixed, and asserting it pins the reference point rather than assuming it. spec ↗ | script | … | |
invalid-radius-keyword-rejected |
The keyword set is closed: a plausible-looking value outside it must not parse, or the parser would be accepting nonsense as a shape. spec ↗ | script | … |