← back to v157 · ship-anchor-visible-and-anchor-valid-and-deprecate-the-plural-versions
conformance · v157
v157 · ship-anchor-visible-and-anchor-valid-and-deprecate-the-plural-versions — conformance probe
6 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
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
singular-anchor-visible-parses |
The renamed singular value `position-visibility: anchor-visible` is accepted. spec ↗ | script | … | |
singular-anchor-valid-parses |
The renamed singular value `position-visibility: anchor-valid` is accepted. spec ↗ | script | … | |
plural-anchors-visible-still-parses |
The plural `anchors-visible` is DEPRECATED, not removed — this proposal explicitly keeps the old names working as aliases, so a stylesheet that never migrated must not break. spec ↗ | script | … | |
plural-aliases-to-singular |
Setting the plural `anchors-visible` serialises back as the singular `anchor-visible` — the observable signature of an alias, as opposed to two independent values that merely both parse. spec ↗ | script | … | |
dual-write-resolves-to-singular |
The forward-compatible migration pattern works: declaring the plural then the singular leaves the singular in effect, because the later valid declaration wins the cascade. spec ↗ | script | … | |
singular-values-compose |
Both singular conditions can be combined in one declaration, as the plural forms could. spec ↗ | script | … |