Spell check disabled in Firefox
Aren Cambre - July 6, 2008 - 03:00
| Project: | TinyMCE |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Description
When running TinyMCE in Firefox 3.0, Firefox's native spellcheck is disabled.

#1
http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/gecko_spellcheck says this is actually default configuration.
http://drupal.org/node/135150 suggests the fix isn't really causing problems.
Patch attached.
#2
Updating status.
#3
please use unified format and patch from the drupal root, see http://drupal.org/patch/create
#4
# diff -u modules/wysiwyg/editors/tinymce.inc.orig modules/wysiwyg/editors/tinymce.inc
--- modules/wysiwyg/editors/tinymce.inc.orig 2009-06-06 20:02:14.000000000 +0100
+++ modules/wysiwyg/editors/tinymce.inc 2009-06-06 20:03:09.000000000 +0100
@@ -128,6 +128,7 @@
// TinyMCE's URL conversion magic breaks Drupal modules that use a special
// syntax for paths. This makes 'relative_urls' obsolete.
'convert_urls' => FALSE,
+ 'gecko_spellcheck' => TRUE,
);
if (isset($config['apply_source_formatting'])) {
$init['apply_source_formatting'] = $config['apply_source_formatting'];
#5
For 2.0 release:
# diff -u wysiwyg/editors/tinymce.inc.orig wysiwyg/editors/tinymce.inc
--- wysiwyg/editors/tinymce.inc.orig 2009-06-12 18:36:27.000000000 +0100
+++ wysiwyg/editors/tinymce.inc 2009-06-12 18:36:55.000000000 +0100
@@ -156,6 +156,7 @@
// HTML control characters and invisible characters. TinyMCE always converts
// XML default characters '&', '<', '>'.
'entities' => '160,nbsp,173,shy,8194,ensp,8195,emsp,8201,thinsp,8204,zwnj,8205,zwj,8206,lrm,8207,rlm',
+ 'gecko_spellcheck' => TRUE,
);
if (isset($config['apply_source_formatting'])) {
$settings['apply_source_formatting'] = $config['apply_source_formatting'];
#6
@Tom
Almost there! check out http://drupal.org/patch/create, under Quick start example (diff). You want to run something more like
diff -up path/to/file/example.module path/to/file/exampleNew.module > mypatchname.patch, and then attach the resulting file to this issue, and set the Status field to "needs review". This will let the maintainer know that you've got some code for him/her to look at, and its easy for them to download and apply your patch with one command.