Support of as you type mode for editors based on a custom data model.WProofreader fully supports ‘as you type’ mode in a wide range of WYSIWYG editors with a custom data model and virtual DOM such as CKEditor5, Quill, Trix, ProseMirror, Scribe.
Accessibility compliance updates. The green color that was used for check-boxes and radio-buttons in the Options and Languages settings tabs has been replaced with the contrast one. This is required to by WCAG 2.1 and Section 508 accessibility standards.
2. Global Custom Dictionary
Simplified global custom dictionary management. With the new mechanism in the Global Custom Dictionary functionality, there is no need to regenerate the activation key. The dictionary will be automatically enabled in 10-15 mins.
Enabled customDictionaryIds parameter. Once a dictionary is created, a unique dictionary ID is assigned to it. This IDs with customDictionaryIds parameter can be used to implement more flexible approach in your app.
[WP-2556] The Slovenian (sl_SL) language doesn’t work.
1.2. API documentation updates.API documentation is updated with the descriptions of the following parameters: autoSearch, enableAutoSearchIn, disableAutoSearchIn.
enableAutoSearchInInputs option is no longer supported as it was replaced by enableAutoSearchIn.
[WP-2380] WProofreader: Focused state is missing when using keyboard navigation between Options, Languages, Dictionary, About tabs.
[WP-2421] WProofreader: Incorrect area-label name for the opened state of the WProofreader Dialog icon.
[WP-2442] WProofreader: Incompatibility of WProofreader with Froala Editor. Incorrect behavior of getFocusableElements in component.js in place with querySelectorAll and passed array (convert array to string).
[WP-2426] WProofreader plugin for WordPress: Extra element appears on hovering a misspelled word when using WordPress (Admin).
[WP-2420] Personal User Dictionary: After removing a dictionary, the words are not underlined and considered as incorrect.
[WP-2450] Global Custom Dictionary: Dictionary doesn’t work after its renaming. Words added to the dictionary are of no effect.
1.1. Compliance with International Web Accessibility Standards (WCAG 2.1) & Keyboard Navigation
With this update in WebSpellChecker Proofreader 1.2, we have introduced a bunch of updates to meet the requirements of the international web accessibility standards from W3C Web Accessibility Initiative (WAI). Specifically, we relied on the Web Content Accessibility Guidelines (WCAG), including WCAG 2.0 and WCAG 2.1.
1.2. Additional Notifications and Progress Indicators
Spinner. Spinner on the dialog panel that is aimed indicating the progress of proofreading. Once the proofreading process is completed, the spinner will disappear.
Save changes. We added an extra notification, warning you from leaving the dialog with changes unsaved (without clicking ‘Finish Checking‘). This is made to prevent accidental loss of your proofreading results.
2. Grammar engine is updated for 8 languages
As a part of this upgrade new and improved grammar rules for the next languages: Catalan, Dutch, American and British English, French, German, Portuguese, Russian, and Ukrainian.
[WP-2384] WSC Proofreader: <span> elements of Proofreader are saved to DB of WordPress&Other systems and after saving are displayed on front-end.
With the release 5.2.2 we stopped support of old plugins and list of the integrations that were based on the older products.
SCAYT plugin for TinyMCE 4 WSC Dialog plugin for TinyMCE 4 WSC Dialog for HTML Editable Controls
However, instead we are offering much better and flexible integration with WSC Proofreader. It can be easily integrated with almost any WYSIWYG editor, including classic HTML editable elements.
1.2. Improved notifications on the UI when working with user dictionary to bring clarity to your users. Check our video to learn more about notifications and how to use personal user dictionary with WebSpellChecker Proofreader.
While providing you with the proofreading tools and services, we gradually implemented your suggestions on making the spell- and grammar checking more convenient. Still, there’s a limit of brushing up the old products. To make the tangible change, we decided to create a whole new solution, based on your and other customers’ ideas on how proofreading should be done in the modern Web. Today we are happy to introduce you the all-new Proofreader. We hope it will become just what your users and your development team lacked for their spell- and grammar checking needs.
The Change: All Proofreading Modes in One Place
From now on you don’t have to sacrifice one usage scenario in favor of the other. The Proofreader comprises the proofreading modes, which were previously available only in separate products. Now your app’s users can decide how they want their text proofread: be it correcting mistakes as they type, or hasteless proofreading of all the text at once in a separate dialog.
On the technical side the Proofreader is all about minimizing the manual integration work:
A single script for all fields. Whichever types of editable fields you have in your app, there’s just a single Proofreader script, to enable spell- and grammar checking in all of them at once. Even in CKEditor 5, which is currently lacking of the built-in way to proofread.
There is wide list of other editors available, we haven’t test it everywhere. If you have an editor that is outside this list, it doesn’t mean that Proofreader won’t work there. We encourage you to try first and see if it works. In case you experience any troubles with the integration, reach us, and we will try to help.
Self-sustaining proofreading. Whenever you need to add new editable fields in your app, the Auto-search functionality of the new Proofreader will detect them and enable the proofreading automatically.
Somehow it feels better to work with good-looking tools. Just remember how jotting the first words in a new crispy notebook feels. When designing the new Proofreader we wanted to make checking spelling and grammar clean and comfortable, thus making it play for your app’s overall interaction experience. Here are the core UI changes:
The suggestion box is simplified. We’ve hidden rarely-used toggles and switches leaving only the primary task of choosing the correct words in the plain site.
Hover for suggestions. No clicking necessary. Spelling and grammar suggestions for marked words appear on mouseover. A subtle tactile change, making proofreading feel even more effortless.
Tuning up became easier. All the necessary settings are now always at hand under the neat badge in the bottom right corner.
Simple, but Not Plain
As easy as it looks the Proofreader is powered by the mighty WebSpellChecker proofreading engine, providing spell checking in 16 default and 152 additional languages, and grammar checking in 14 out of 16 default languages in all modern browsers.
2. New API Options for ‘autoSeach’
We added two new API options that give more control over the autoSearch functionality of WebSpellChecker Proofreader. By default, Proofreader with the enabled ‘autoSearch’ option will be enabled in all supported editable fields on the page. However, we understand that this might be inconvenient, as there might not be a need to check some types of editable fields. Now you can choose where you want disable Proofreader.
You can disable Proofreader in any type of editable field by class, id, data attribute and elements.