Closed Bug 1113109 Opened 10 years ago Closed 8 years ago

[CKEditor 4] Add support for non-English spell check dictionaries

Categories

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

All
Other
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sheppy, Unassigned)

Details

(Whiteboard: [specification][type:feature])

What problems would this solve? =============================== The CKEditor 4 upgrade adds spelling suggestions to the right-click context menu, but these suggestions are always in English, regardless of what language you're editing. We need to use the dictionary corresponding to the language being edited. Who would use this? =================== Localization teams. What would users see? ===================== Spelling suggestions in their language. What would users do? What would happen as a result? =================================================== Spell checking that works correctly, as expected. Is there anything else we should know? ====================================== We could, optionally, offer the ability to select a dictionary other than the default for the page language. This does NOT block launching CKEditor 4.
BTW, the reason this doesn't block is that the current system is already an improvement over what we had before.
Severity: normal → enhancement
Component: General → Editing
FWIW, this has previously been addressed by making possible a simple switch from the CKEditor spellchecker to the browser spellchecker. In the prior version we had to write a plugin to allow this switch, but perhaps the new version provides an easier way to accomplish this? I was able to simulate the earlier plugin's effect by using devtools to edit CKEditor "body" element to have spellcheck="true" (it is set to "false" by default): <body class="text-content redesign cke_editable cke_editable_themed cke_contents_ltr cke_show_borders" contenteditable="true" spellcheck="true"> When that is set to true, people can CMD/CTRL + click to see the context menu they see in non-CKEditor textarea inputs. Which means having access to all the browser-configured locales they're used to.
This is resolved with the PR I submitted yesterday for bug 1318827.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.