You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spell checking on Edge does not work correctly. If spell checking is OFF then Edge won't do it.
If you toggle spell checking ON then the list of spelling options in the right+click context menu are missing. If you cannot spell a word, you have to copy it into Bing or Word to get a suggestion.
Also, the spell checking that Ghost uses is not at all accurate for English (UK/Australia).
Steps to Reproduce
Turn off spell checking
Edge's native spell check is supressed
Turn on spell checking
Right+Click on a word - the list of spelling options are missing
If the spelling is OFF then I think the browser spell checker should be enabled. At the moment, there is zero benefit from the Ghost spell checker over Edge.
Technical details:
Ghost Version: 1.17.2
Node Version: no idea, using Pro
Browser/OS: Edge
Database: mysql
The text was updated successfully, but these errors were encountered:
This is known and unfortunately the expected behaviour for the markdown editor. Spell check for rich-text will eventually land as part of the full mobiledoc editor.
Issue Summary
Spell checking on Edge does not work correctly. If spell checking is OFF then Edge won't do it.
If you toggle spell checking ON then the list of spelling options in the right+click context menu are missing. If you cannot spell a word, you have to copy it into Bing or Word to get a suggestion.
Also, the spell checking that Ghost uses is not at all accurate for English (UK/Australia).
Steps to Reproduce
Turn off spell checking
Edge's native spell check is supressed
Turn on spell checking
Right+Click on a word - the list of spelling options are missing
If the spelling is OFF then I think the browser spell checker should be enabled. At the moment, there is zero benefit from the Ghost spell checker over Edge.
Technical details:
The text was updated successfully, but these errors were encountered: