Browsers flag misspellings in contenteditable/textarea fields but expose no suggestion API to JS, so any friendlier UX (click a flagged word → popover with corrections and synonyms) requires the editor to ship its own dictionary pass (e.g. hunspell/nspell + ProseMirror decorations) — too invasive to patch from outside. Requesting first-class editor support: spellcheck decorations with a suggestions/synonyms popover across PT editors and plain text fields. We'd use it on day one.
Browsers flag misspellings in contenteditable/textarea fields but expose no suggestion API to JS, so any friendlier UX (click a flagged word → popover with corrections and synonyms) requires the editor to ship its own dictionary pass (e.g. hunspell/nspell + ProseMirror decorations) — too invasive to patch from outside. Requesting first-class editor support: spellcheck decorations with a suggestions/synonyms popover across PT editors and plain text fields. We'd use it on day one.