← back to v153 · spell-check-custom-dictionary-api

conformance · v153

v153 · spell-check-custom-dictionary-api — 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.

browser: spec: https://github.com/whatwg/html/pull/12590 chromestatus: #6185007701557248 generated 2026-08-28T00:00:00Z by claude-opus-5-v153-build
0
pass
0
fail
0
blocked
7
total
id contract kind verdict detail
document-exposes-the-custom-dictionary The feature itself, and the recommended feature test: a browser with spell checking exposes the attribute on the document, and one without must not expose it at all. spec ↗ script
the-dictionary-has-addwords-and-removewords Two methods, both taking a sequence — so a glossary is one call rather than a loop, and a page that changes context can take its terms back out again. spec ↗ script
the-dictionary-cannot-be-read-back Write-only by design. An enumerable dictionary would report what a user has been typing and would fingerprint them by what a page had already added, so the absence of any reader is part of the contract rather than an omission. spec ↗ script
the-attribute-is-the-same-object-each-time [SameObject]: reading the attribute twice must give the same dictionary, so a page can hold a reference rather than re-reading, and two parts of an application cannot end up talking to different lists. spec ↗ script
addwords-accepts-a-sequence The argument is a list of strings. Calling it with a real glossary must not throw — this is the call every page using the feature will make. spec ↗ script
a-secure-context-is-the-precondition [SecureContext]: the attribute is withheld outside one. Asserted here so that an absent attribute can be attributed to the browser rather than to the page — if this fails, the feature check above proves nothing. spec ↗ script
spellcheck-is-still-controllable-per-element The workaround this feature replaces must keep working: the spellcheck attribute reflects and can be turned off per field. A dictionary is an improvement on that switch, not a replacement for it. spec ↗ script