3 ms·
Would this even apply to something like TinyMCE? I thought (read:assumed) the in-browser spell checking only worked against textarea's and text inputs.
by joekrill 14y ago
Would this even apply to something like TinyMCE? I thought (read:assumed) the in-browser spell checking only worked against textarea's and text inputs.
- omgmog 14y agoIn TinyMCE you get both the browser-based spell checkers (via the right click context menu), and the spelling suggestions in TinyMCE (depending which spelling backend you're using: aspell, enchant, google spell, etc. http://www.tinymce.com/wiki.php/plugin:spellchecker http://www.tinymce.com/wiki.php/plugin:spellchecker)
- Valien 14y agoWe use TinyMCE and a .NET plugin that uses the GoogleSpell check service. It's dead right now and we are trying to find a solve for it.
- passionfruit 14y agoI decided to use Yandex Speller since at the time I was researching this issue it was clear that Google Spell was an undocumented and unsupported feature. http://api.yandex.ru/speller/ http://api.yandex.ru/speller/
- ffk 14y agoAccording to the TinyMCE, you can use aspell. http://www.tinymce.com/wiki.php/Plugin:spellchecker http://www.tinymce.com/wiki.php/Plugin:spellchecker You can get a windows build of aspell at http://aspell.net/win32/ http://aspell.net/win32/ Instructions are on the wiki on how to wire it up.
- lini 14y agoMost (if not all) WYSIWYG HTML editors like TinyMCE use a contenteditable container (e.g. div) and all current browsers offer spell check in the contenteditable element.
- lifeisstillgood 14y agoIt actually is a TinyMCE problem. (Article says that Tiny used the non public URL and if it got back 500 error, just defaulted to "oh, no spelling errors then")