[upstream] Correcting spelling via native right-click context menu in CKEditor-enabled text fields is impossible

It seems you've read #2307141: Enable browsers' (native) spell checker in CKEditor and the difficult weighing of choices we did there. There is no great choice, it's always choosing the lesser of two evils.

I don't see how making disableNativeSpellChecker configurable would help at all. It's set to FALSE so that at least you get the red underlining of incorrectly spelled words. If you change it to TRUE, then you won't even have that.

So, I'm afraid this is a case of Closed (works as designed), sadly :(

Currently I see ONLY "Paste ctrl-V" when I right click on a misspelled word. THAT is a BUG!!
(Win 10 Firefox 53)

IF you're going to show the user the red underline for misspelled words, and can't give them something that WORKS AS IT SHOULD, it's better to show the user NOTHING - in other words disable right-click, don't show them erroneous information/possibilities. OR tell them in a tooltip/right click something USEFUL like "ctrl or command right click to correct spelling".

Or DO NOT show the underlined misspelled words at all - in other words don't give them false hope.

Or make it work like it should!

+1 it isn't a great user experience to begin with for CMS users to have to use ctrl + right click, let alone end users.

I agree that this behaviour is confusing, I have just thought it was a D8 bug.

I believe expected behaviour is that when an item is highlighted as misspelled by being underlined in red, a right mouse click will present spelling suggestions. This is the behaviour in CKEditor in D7 - and it's also the behaviour in this text box I'm typing this comment in now.

IMO it's an important part of usability and the editor experience which is important. Even reading through the comments here I'm unsure how I would explain the behaviour to a client if it is decided it's working as normal "the word is underlined in red because it's misspelled, go get a dictionary and figure it out"? :)

Screenshot of error and right mouse click:

#6 + #8 + #9: that may very well be, but there's nothing we can do to fix this. It's a browser limitation. Drupal can't fix that.

#7: no need to be rude.

#9:

I believe expected behaviour is that when an item is highlighted as misspelled by being underlined in red, a right mouse click will present spelling suggestions.

This has never been an expectation for me. The underlining itself is sufficient for me: I'll fix it myself, because very often, the suggestions include lots of wrong suggestions too. So, for me, just the underlining is sufficient. And coincidentally, that's also as far as browser limitations will let CKEditor go.
Again, please read #2307141: Enable browsers' (native) spell checker in CKEditor for the full discussion. Specifically, see #2307141-6: Enable browsers' (native) spell checker in CKEditor.

We have to choose between either:

• spell checking with only underlining, no right-click-to-correct, but DO retain the CKEditor context menu
• spell checking with underlining and right-click-to-correct, but DO NOT retain the CKEditor context menu

There's no good choice.

I'm personally okay with removing the CKEditor context menu, so that this would become possible. But doing so would be a backwards-incompatible change.

If it'd help, I'm happy to create a Drupal 8 contrib module that disables the CKEditor context menu, so that you can use the native context menu, and hence do get spelling/grammar corrections.

But do note that this was discussed at length in #2307141: Enable browsers' (native) spell checker in CKEditor…

Of course! :)

Reflecting #11.

Thanks Wim - apologies for going over old ground. I work with not for profits and government so they get hung up on stuff like this, and worse they add it to long lists of requirements that rule a tender out.

Interested in where the govcms people in Australia go with this - they should have need for restricted ckeditor + spell check. I'm thinking the D8 contrib module is probably a good idea.

Agree with Rachel that leaving this open is worth it, also for ease of identifying how there is an issue. The Enable browsers' (native) spell checker in CKEditor task is great and comprehensive but long.

Just to put my two cents: there are two most reasonable ways to go either use SCAYT with CKEditor's custom context menu or you can go with native spellcheck and native context menu.

Going without a possibility to correct typo from a context would be an annoyance for certain group of end users.

I'd suggest going for going SCAYT + custom context menu. SCAYT integrates well with CKE (undo and whatnot), provides the same cross-browser experience.

Also dropping custom context menu will result with users not being able to use tabletools plugin utility, which ATM is the only way to access certain features, such as drop a column etc. It's a flaw that we want to fix in future releases, but that's how it works now.

Having above in mind I'd go with SCAYT now, and revisit it in year or two to see if target browsers have provided APIs for context menu customization.

SCAYT (http://ckeditor.com/addon/scayt) is not an option, because it depends on a 3rd party service.

I needed an immediate solution for some of my clients, so I created a project that disables the contextmenu, tabletools, and tableresize plugins via a tiny module:

https://www.drupal.org/project/ckeditor_browser_context_menu

I would love for this to be a customizable option in the CKEditor module itself.

Lets leave this issue open, but I am also keen on not fixing a standard CKE behaviour unless we solve it on the editor level itself.

In case you can't use SCAYT, then your only option (keeping spell check) is to use native context menu.

CKEditor has no way to manipulate browser spell checking (no API), so this function can only be manipulated only using native context menu.

There's a feature in CKE4 (enabled by default) that ctrl/cmd+click gives you a native context menu (see "Using Native Browser Spell Checker" in https://sdk.ckeditor.com/samples/spellchecker.html).

#19 Thank you diamondsea, great workaround!

CKEditor has been removed from core, CKEditor 4 is removed from Drupal Core in 10.0.0