Closed Bug 1351022 Opened 8 years ago Closed 5 years ago

Use browser-based spellcheck instead of 3rd-party hosted spellcheck (SCAYT)

Categories

(developer.mozilla.org Graveyard :: Editing, enhancement, P3)

Product:
developer.mozilla.org Graveyard
Component:
Editing
Platform:
All
Other
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jwhitlock, Unassigned)

References

Details

(Keywords: in-triage, Whiteboard: [specification][type:change])

What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== The CKEditor includes the SCAYT plugin, to integrate spellcheck with the CKEditor experience. When editing a MDN wiki page, it needs to be enabled by selecting the spelling menu (the icon is "ABC" over a checkmark) and "Enable SCAYT". This loads 3rd-party assets and sends some content to a 3rd-party server. We don't currently have a license with SCAYT, and use the default CKEditor license, which includes ads. License and API limits prevent us from turning on this feature for all editors. Instead, MDN can use browser-native spellcheck. What problems would this solve? =============================== Browser-native spellcheck has no license or API restrictions, meaning it could be enabled for all editors by default. It may be better for language support and customization (such as bug 1113112). On the other hand, CKEditor does not support browser-native spellcheck as an integrated experience. It would require disabling the CKEditor context menu, or instructing editors how to access the browser spellcheck using an alternate method (such as Control + Right Click). Who would use this? =================== MDN editors What would users see? ===================== The browser would identify misspelled words, for example with a squiggly red underline. If they hold Control while Right-Clicking, then they can access suggestions, or add to a personal dictionary. What would users do? What would happen as a result? =================================================== Users would be more likely to notice and fix misspellings. Is there anything else we should know? ====================================== This issue was first discussed in bug 1318827. A dev-mdc discussion: https://groups.google.com/forum/#!topic/mozilla.dev.mdc/2aUzNXWbV2I A tech document outlining alternatives: https://docs.google.com/document/d/1189WsFRmoFVGHSXgJyuTOZeL3nvKr3NyBIvI-TZeJ6M/edit
Summary: Use browser-based instead of 3rd-party hosted spellcheck (SCAYT) → Use browser-based spellcheck instead of 3rd-party hosted spellcheck (SCAYT)

Might be solved by CKEditor 5.

Priority: -- → P3

CKEditor 4 shipped with SCAYT as a way to integrate with https://webspellchecker.com. CKEditor 5 does not ship with SCAYT or a built-in spellchecker. From the CKEditor 5 Migration document, it appears that the scayt_* and wsc_* variables are no longer available, and disableNativeSpellChecker has been removed as well. It is unclear if SCAYT will return as a add-on plugin for CK5, or if native spell checker will be the only supported solution.

MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.