Posted by toddgee on April 7, 2010 at 3:42am
Jump to:
| Project: | CKEditor - WYSIWYG HTML editor |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
with the fckeditor module, one could configure the editor to use the firefox built-in spell checker by including the lines:
FCKConfig.FirefoxSpellChecker = true ;
FCKConfig.BrowserContextMenu = true ;
in the fckeditor.config.js file. Is there any way to do something similar with editor?
Comments
#1
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;#2
thank seems to work. Closing this issue.
For others that stumble on this, there's more of the same here:
http://stackoverflow.com/questions/2682042/ckeditor-using-firefox-built-...
http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.config.html
#3
Automatically closed -- issue fixed for 2 weeks with no activity.
#4
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 ...
#5
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!
#6
Great - thanks - just the easy to understand explanation for everyone -
#7
What should we do if the user, uses another browser?