Enable browser native spell checker by default (Backport for D7)

You can re-enable the firefox spellchecker like so:

config.disableNativeSpellChecker = false;

Unfortunately, I haven't found a way to disable the CKEditor menu. You can, however, control-click to get the native one. If it doesn't work, look for this is in your config, and change it to true (or remove it - the default should be true).

config.browserContextMenuOnCtrl = false;

Sorry, but could you add just with a littler more detail where to put the line:

config.disableNativeSpellChecker = false;

Which file and which subdirectory - I tried but failed to get it going.

Is that the only line of is there something else to put around it?

Thanks ...

You add the line to your ckeditor.config.js file. This file is where all your customizations can go for the module, such as creating custom toolbars.

The file is in the ckeditor module folder. In my setup this folder is located at: /sites/all/modules/ckeditor

You can add the line right before the closing }; tag. I also suggest adding a comment explaining what the line is for. This is a good way to track any customizations and copy them over when you update the module in the future.

Hope that helps!

Great - thanks - just the easy to understand explanation for everyone -

What should we do if the user, uses another browser?

Adding lines to ckeditor.config.js file works very good, but why this is absent in module settings? It is very useful for many users, but not each user can find this issue and do operations with files.
I change this issue to "Feature request" and hope that this will be available in module settings.

I close this ticket.
This option will not be added to module settings. It is for more advanced users who can add this in ckeditor.config.js file or in "Custom JavaScript configuration" option in CKEditor's profile.
Too many options in module settings can be confused for less advanced users.

.... slightly puzzled and wondering about this view:
"This option will not be added to module settings. ... Too many options in module settings can be confused for less advanced users.

I would have thought that proper spelling is such a fundamental aspect of developing successful websites, that it should be a basic feature rather than an advanced one.

@tryitonce is correct: spell checking is such a basic thing now, it doesn't make sense to omit this option, only allowing advanced users to find it. In fact, the native spell checker should be enabled by default. Drupal is about usability, right?

As late comers from fckeditor to ckeditor we too stumbled over the spell checker configurations. For our users spellcheckers are essential.

This information is taken from many posts available on the Internet.

To configure ckeditor for:

• browser spellcheckers for those browsers that include one
• and server installed spellcheckers such as Aspell/SpellerPages

When using the ckeditor module edit the file ckeditor.config.sys ckeditor.config.js in the module directory. If using the ckeditor library with another module such as wysiwyg edit the file config.sys in the ckeditor library directory. Copy and paste the following into the configuration file and uncomment or comment as needed.

/**
* To activate Spellchecker browser side uncomment following lines
* second line (default setting, can leave commented) allows access to browser context menu with ctrl-right-click
* otherwise there is no access to the browser context menu without further config changes
*/
config.disableNativeSpellChecker = false;
// config.browserContextMenuOnCtrl = true;

/** NOT TESTED
* For browser default context menu on right-click rather than ctrl-right-click
* Note: Disabling Ckeditor's context menu may render it impossible to work with tables
* uncomment following lines;
* three plugins need to be removed because scayt depends on menubutton which depends on contextmenu
*/
// config.browserContextMenuOnCtrl = false;
// config.removePlugins = 'scayt,menubutton,contextmenu';

/**
* Spellcheckers - server side - add Aspell/SpellerPages
* get Aspell plugin for ckeditor
* see http://cksource.com/forums/viewtopic.php?f=11&t=15893
* Download from http://cksource.com/forums/download/file.php?id=512
* check aspell/pspell is installed on server and working
* download Aspell plugin to modules/ckeditor/plugins/aspell
* uncomment following lines to add aspell and remove scayt
* add 'SpellCheck' to toolbar options
* if aspell/pspell directory on server is different than default
* edit file aspell/dialogs/aspell.js and change location in Speller.spellCheckScript
*/
config.extraPlugins = 'aspell';
config.SpellerPagesServerScript = 'server-scripts/spellchecker.php' ; // Available extension: .php .cfm .pl
config.removePlugins = 'scayt';
};

/*
* Sample toolbars
*
* Note: Default ad supported spellchecker option name is 'SpellChecker'
* When using aspell remove the default option name and use aspell's toolbar name 'SpellCheck'
* Also remove the 'Scayt' option
*/

After making changes to the configuration files, flush website caches and browser cache.
To activate the Aspell spell check it is also necessary to go to admin/settings/ckeditor and edit each profile. Open up the "Editor appearance" fieldset. Under Toolbar, Load sample toolbar, click on required toolbar to refresh icons. Then below the icons under Plugins check the Aspell plugin.

The Aspell/SpellCheck icon does not appear on the configuration toolbar displays but does appear when using editor.

It might be helpful to other newcomers to have this in the default ckeditor.config.sys with all the lines commented.

Sorry I forgot to change the status and have done that now.

@izmeez, u write instruction for WYSIWYG module or CKEditor module?

The instructions in comment #13 are for the ckeditor module.

@izmeez ,
there is no ckeditor.config.sys file into CKEditor module for drupal. Did you mean ckeditor.config.js ?

Sorry, that is correct it should be ckeditor.config.js

There is no patch yet.

@jcisio Are you looking for #13 copy and paste to be made into a patch?

I agree this should be an option in the module or else the default. I spent half a day figuring it out because I am one of the "not advanced coders" deemed unfit to allow my site users to use their own browser spell checkers instead of the premium one. Figuring this out has confused me significantly more than an extra button in the configuration panel would have done.

This works with my Drupal 7.27 development site.

go to sites > all > modules > wysiwyg > editors > js
and edit the file: ckeditor-3.0.js

Insert the following line of code (I put it near the bottom and have no idea if that's proper, but it works):

config.removePlugins = 'contextmenu,liststyle,tabletools';

It's very interesting to note that drupal.org's rich text editor does not rip away your browser's native spellchecker. This should be a clue for the developer that this is the direction wysiwyg should be going as well. I understand Drupal 8 will ship with ckeditor in core and hope this issue will be addressed there. I hope this post will save someone like me the time I spent with trial and error figuring out where the heck to stick the line of code I found in my searching because when wysiwyg is involved, it doesn't go where most posts are suggesting it should go (in the ckeditor folder).

This should be an option. I forced it in ckeditor.inc, but a switch checkbox would be nice. Same with 7.x

Attached is a patch for ckeditor-7.x-1.x-dev consistent with D8 implementation #2307141: Enable browsers' (native) spell checker in CKEditor committed to 8.1.x

The patch adds entry to help and enables browser native spell checker by default but requires use of ctrl-right-click or command-right-click (MAC) to retain ckeditor context functionality.

This needs tests and needs review.

Changing title to highlight this is Backport for D7

Is CTRL+Right Click for native menu click functionality browser dependent? I tried with Firefox and Chrome with no success while it seems to work in Opera and Chromium. Quite confused.

EDIT: Found it - Issue is caused by gesture addon in the browser.

Any chance patch in #23 can be RTBC ?