GNOME Bugzilla – Bug 783353
Composer spell checks with no language selected
Last modified: 2017-06-08 08:55:45 UTC
Description: Having no selected language for spellchecking still checks the spelling (using the user’s current locale?), but the spellchecking UI is disabled. Steps to reproduce: 1. Install Fedora 26 with US English locale 2. Open up Evolution, [setup an account], and start composing a message. 3. Type in the following in the body section: dmeonstrate teh isue All three words will be highlighted with a red squiggly line, as none of them use proper English. 4. Right-click on any of the three words. Expected: A spellchecking UI in the context-menu. Actual: The context-menu don’t have any of the spellchecking related UI elements. The words are identified as having being incorrectly spelled in my default language, but I can’t actually resolve the spelling issues from the context-menu. Work-around: 5. Open up the Edit menu and select Current languages, and check the box next to English (US) [no language will be checked in the menu by default] 6. Right-click on any of the three words again. This time the spellchecking UI will be present. Notes: I’ve actually noticed this several times over the last couple of years on newly installed systems. However, as I already know how to work-around it I’ve never remembered to report a bug. Should be fixed as the spellchecker appears to be broken for new users. Either don’t ‘squicggly-line’ the incorrectly spelled words when no language is selected, or always enable the same dictionary that is used by default to ‘squiggly-line’ them. Version: 3.24.2-1.fc26.
Thanks for a bug report. It was some sort of disagreement in the code. Removing all languages from Edit->Current Languages in the composer disabled spell checking, but the same after composer open left the spell checking on. I made some necessary changes and it behaves properly now. Hmm, properly, I noticed that enabling spell checking doesn't re-test the document (or the part currently visible in the view), but that feels more like a WebKit issue, than Evolutions. Created commit f2717be in evo master (3.25.3+) Created commit 1c0fdb1 in evo gnome-3-24 (3.24.3+)