← back to v150 · case-sensitive-anchor-name-matching-in-quirks-mode
conformance · v150
v150 · case-sensitive-anchor-name-matching-in-quirks-mode — conformance probe
7 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
7
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
document-compat-mode-detectable |
document.compatMode reports CSS1Compat (standards) or BackCompat (quirks); the change targets BackCompat documents. | script | … | |
named-anchor-lookup-via-getelementsbyname |
getElementsByName is case-sensitive in all modes — used as a parallel surface that already matched what fragment navigation now does. | script | … | |
querySelector-id-case-sensitive |
ID selectors are case-sensitive — the same rule fragment navigation now adopts in quirks mode. | script | … | |
quirks-iframe-fixture-enters-backcompat |
A no-doctype iframe enters BackCompat mode, which is the document mode targeted by the Chrome 150 change. | script | … | |
fragment-navigation-exact-name-in-quirks-iframe |
Chrome 150+ finds the <a name> whose case exactly matches the fragment in BackCompat documents. | script | … | |
fragment-navigation-missing-case-stays-unmatched |
Chrome 150+ leaves a BackCompat fragment unmatched when no <a name> has the exact same case. | script | … | |
html-element-id-attribute-roundtrip |
Element.id round-trips with original case (the DOM has always stored ID with original case; matching is what changed). | script | … |