Back to Release Notes

WebSpellChecker Cloud 5.0.0 Release Notes

End of Support

With release of WebSpellChecker Cloud 5.0.0, we have finally discontinued support of old SCAYT 2 product and all the integrations based on it as a part of the Free services. A year ago we made an announcement in our blog about the planned end of support for SCAYT 2. 

Thus, those who were using Free SCAYT 2 in a bundle with old versions of CKEditor (FCKEditor, CKEditor 3-4.4), no longer have access to spell check as you type feature. Those users are required to upgrade the version of CKEditor to the most recent one.

Breaking Changes

1. Unified WebSpellChecker Application Core – WSCBundle

We have combined bunch of separate applications which used for various integrations with rich text editors and plain HTML editable elements into a single unified bundle application. Previously each integration of our SpellCheckAsYouType (SCAYT) product with CKEditor, TinyMCE, Froala Editor, and HTML editable controls required specifying paths to separate applications JS files. Now we have a single backward compatible application JS file (wscbundle.js) that can be used instead for all these integrations. 

In scope of this change, the following updates have been introduced:

  • SpellCheckAsYouType (SCAYT) for Editable Controls is replaced with a new product called ”WebSpellChecker Proofreader”. At the moment WebSpellChecker Proofreader fully inherits the functionality of SCAYT. 

Going further WebSpellChecker Proofreader will be the main product of WebSpellChecker and will combine functionality of old SCAYT and WebSpellChecker Dialog (WSC) products. Depending on the preferences end users will be able to proofread as they type and/or proofread in a dialog accordingly. Moreover, WebSpellChecker Proofreader will have a special auto-detection mechanism which will be auto-detecting all the editable areas on the page and enabling proofreading functionality for end users.

  • New API for WebSpellChecker Proofreader. The new API inherits the main part options and methods of SCAYT API and compatible. However, some of the options names are changed to make them more precise. Check out our new API for WebSpellChecker Proofreader.

2. New Multi-language Grammar Engine

2.1. Enhanced American and English Grammar Checking

As a part of new AppServer 5.0, the old grammar engine has been replaced with an open-sourced multi-language cross-platform grammar engine – LanguageTool. LanguageTool provides more capabilities, better grammar checking results and available for wider range of languages. With release 5.0.0, advanced grammar checking option is available for American and British English.

In our next release 5.0.1, we will extend the grammar support to 14 languages from the default languages list which comes with the default package. You may check the grammar support availability on the Languages and Specialized Dictionaries Support page.


1. Language Dictionaries Updates

1.1. New Additional Language

  • Added support of the Uzbek Latin language. Check the quality of spell checking on the Uzbek Latin demo page.

1.2. No Longer Supported Languages

  • Manx – Isle of Man (gv_GB) language is no longer available as an additional language.

  • Interlingua (ia_XR) language is no longer available as an additional language.

1.3. Extended and Improved Language Dictionaries

  • Georgian language dictionary has been enlarged with new words. Check the quality of Georgian spell checking on the Georgian language demo page.

  • Swedish language dictionary has been enlarged with two new words: “styrketräning” and “städfirma”.

  • Added missing word “Ensure” to the American/British/Canada English language dictionaries.

2. SCAYT & WProofreader 

2.1. SCAYT & WebSpellChecker Proofreader Badge Button

A while ago we implemented a separate badge button component for SCAYT product. It was initially designed to simplify the SCAYT context menu view and make the focus on the most important actions for end users while they are proofreading. All the auxiliary action items such as settings, enable/disable, etc. will be moved to the easily-accessible badge button. If the badge button is enabled (“enableBadgeButton:true”), end users will see a small orange icon located at the right bottom section of editable area. On hover, an end user will be able to open settings dialog or enable/disable SCAYT.

2.2. Changed Number of Suggestions

The number of suggestions in the more suggestions section in the default view has been set to five (5). Thus, in total, end users will see only eight (8) suggestions, three (3) main suggestions and five (5) more suggestions. The most relevant suggestions are usually at the top of the suggestion list. Administrators of the system can still manage the number of suggestions to be shown to end users using appropriate parameters.

  • Administrators can manage the number of suggestions shown to end users. Depending on the integration, administrator can change the default number of suggestions shown in the main suggestions section and in the more suggestions section using appropriate API options/parameters for each of the integrations. For example, there is a separate option/parameter moreSuggestionsCount for WebSpellChecker Proofreader, that can be used for managing the number of suggestions shown in the more suggestion section.

2.3. Updated User Manual

As a part of introduction of new product – WebSpellChecker Proofreader – based on the SpellCheckAsYouType (SCAYT) product, we have updated previous version of SCAYT User Manual to a new one. As it was already mentioned, at the moment there is no dramatic difference between SCAYT for Editable Controls and WebSpellChecker Proofreader. However, going further we will be introducing more and more new features in WebSpellChecker Proofreader. 

Bug Fixes

  • GitHub #141: SCAYT plugin for CKEditor: SCAYT throws Uncaught Error: Error in Rangy WrappedRange module: createRange(): Parameter must be a Window object or DOM node
  • GitHub #153: SCAYT plugin for CKEditor: Chrome. Correcting word in widget moves focus to another editable
  • GitHub #155: SCAYT plugin for CKEditor: SCAYT throw an error on IE8 and doesn’t work
  • GitHub #156: SCAYT plugin for CKEditor: SCAYT doesn’t seem to work on IE10
  • [WP-1608] – SCAYT plugin for CKEditor: After some text is drag & dropped, markup is not refreshed for grammar problems
    [WP-1634] – WSC plugin for CKEditor: Request to FastCGI fails when user tries to replace word with non-English characters with a proper suggestion
  • [WP-1560] – SCAYT Core: CTRL+Z removes focus in FireFox
    [WP-1518] – SCAYT for Editable Controls: Backspace after Enter removes markup
  • [WP-1579] – SCAYT for Editable Controls: No focus set on the input filed of Dictionary tab
  • [WP-1581] – SCAYT for Editable Controls: Dictionary preferences are not keyboard operable
  • [WP-1601] – SCAYT for Editable Controls: User Dictionary: Incorrect message is shown if user tried to create a dictionary with space(s) instead of name
  • [WP-1652] – SCAYT for Editable Controls: Context menu doesn’t work with “enableOnTouchDevices = true”
  • [WP-1753] – SCAYT for Editable Controls: Spell check and grammar check does not work on touch devices
  • [WP-542] – Web API: Duplicated misspelled words result in duplicated response
  • [WP-562] – Web API: Wrong position result is returned if a misspelled word has number
  • [WP-574] – Web API: User Dictionary: No validation for an empty parameter “new_name”
  • [WP-1247] – Web API: User Dictionary: “getdict” command doesn’t return “wordlist”