← back to v153 · remove-non-standard-navigations-targeted-at-current
conformance · v153
v153 · remove-non-standard-navigations-targeted-at-current — conformance probe
4 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
4
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
target-reflects-verbatim |
The target IDL attribute reflects its content attribute with no normalisation, so a non-standard value such as _current survives round-tripping and the case of it is preserved. This is what lets a page audit its own markup for the removed keyword. spec ↗ | script | … | |
a-frame-name-may-begin-with-an-underscore |
The name content attribute of an iframe is stored verbatim, so a browsing context genuinely named _current can exist. The removal matters precisely because such a frame was unreachable by name from Chrome while the keyword existed. spec ↗ | script | … | |
every-targetable-element-carries-the-same-attribute |
A target is a browsing-context name in all four positions the standard defines it in — a, area, form and base — which is why a removal of one keyword has to be audited across all of them rather than just in links. spec ↗ | script | … | |
a-named-frame-is-reachable-by-its-name |
Ordinary name lookup — the mechanism the removal returns _current to. A frame carrying a name appears under that name in the containing window's frame list, which is the step the extra keyword branch used to skip. spec ↗ | script | … |