Red Hat Bugzilla – Bug 978088
Spell checking no longer works in Chrome on initial load
Last modified: 2014-08-04 18:27:35 EDT
Since the change to using web workers for the spell checking, it no longer works in Chrome and fails with the following error:
Just found another interesting part, it only appears to fail when the page is initially loaded. If you do a search or go to a topic directly and then click the topic in the search results pane, the spell checking will start to work.
*** Bug 979196 has been marked as a duplicate of this bug. ***
The issue appears to be because the editor is only waiting for the positive dictionary to load, and is not waiting for the negative or negative phrase dictionaries to load.
Fixed in 201307011121
When QAing bug fixes, please make sure the build you are using is equal to or higher than the build identified above. Be aware that this fix may have only been applied in PressGang Next at this time, or it may not be currently applied in any production system, in which case it can only be verified at a later date.
The issue still remains in Build 201307011121. This is testing in Incognito mode and completely clearing my cache.
Also changing the title to be more descriptive.
Just adding additional details.
Now the spell checking fails earlier by the looks of it. The error is now:
By the looks of it the spell checking is running in a web worker, in which case it doesn't have access to the console object (see: http://stackoverflow.com/questions/7251779/web-worker-console-log or http://www.htmlgoodies.com/html5/client/introduction-to-html5-web-workers-browser-support-non-accessible-elements-and-error-handling.html)
Forgot to mention, that the main problem is that the dictionary is still null.
Fixed in 201307171035
This was an issue with the sequence in which the dictionary data was passed to the worker.
Verified, so setting this to RELEASE_PENDING.