-
Notifications
You must be signed in to change notification settings - Fork 15.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Renderer spellcheck API does not work on Windows #28684
Comments
Previously on #28404 (Issue was erroneously closed and subsequently forgotten). Please consider re-opening original issue if marking this one is as duplicate. This API works on Linux perfectly fine. On Windows, despite the textarea detecting the spell error, the API still returns false. |
A user of one of my apps ran into this same issue, and when I started testing I noticed something strange. It actually does work for some languages on Windows (in my case It works flawlessly on Linux, even before calling the language list API. And keeps working once you do call it regardless of the language list. |
Confirmed this bug too on v12.0.7 / windows 10. Set |
Hey @Jelmerro, thanks for reporting this issue! I just took a look at your Fiddle gist and want to make sure I'm not misunderstanding - when I run the repro, I'm also seeing the test fail going back to (at least) Electron 8.5.5. Can you confirm whether or not this ever worked as expected for your app, or did this break for you in Electron 12? Having that bisect is helpful to us when trying to solve the issue, so I just wanted to double check. |
I did not report this issue, this is just something I ran into when working on one of my projects. It has been an issue for a while, that's why I thought that the other one was related as well. I only added word suggestions in a custom context menu when I was already on electron 12.0.5, but I can also reproduce this for much older versions (I just tested 8.5.5) as well. |
We have the same issue while trying to replace
My wild guess is that this is an issue with the Windows spell checker and Chromium. Maybe we hitting a precondition because Electron expects to use Hunspell but Chromium expects to have a valid platform specific spell checker in the renderer. Unfortunately, I'm unable to build Chromium and hope this can be fixed. For now, both APIs have no functionality on Windows. |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment! |
Don't think this was ever fixed. |
Still not working on Electron 21 |
I can confirm that this bug is still happening on Electron v22. From my own testing, it seems that both English dictionaries (i.e.: The fields Perhaps this is unrelated, but it seems to me like only one language is checked in the textarea itself. Is this expected behaviour? Testcase gist URLhttps://gist.github.com/Fevol/9ec53ef916414737b63eac1ea2a5318b |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment! |
Still seems like an issue if you use the "wrong" dictionary in 24.0.0 on Windows only. |
Also retested using my testcase -- the issue is definitely still present with the latest version (v24.0.0). |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment! |
still an issue |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment! |
still an issue |
I can confirm this still being an issue. The e-mail client Mailspring is affected by it. See:
Some debugging led me to the assumption, that the correct dictionaries may not be downloaded and are therefore not available by Electron. See: #29348 I am using German as my default system language. When I configure e.g. an English dictionary, I get the events that it was downloaded successfully before initializing the spellcheck. When I instruct electron to use German as the spellchecking language, I only get the events fired that the dictionary was loaded. See:
|
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment! |
still an issue. |
can confirm. Still an issue. |
How did you get logging output like this? |
@alex1701c I added some debug logs to the source code to trace the issue. |
@alex1701c you can use electron events to add some logs https://www.electronjs.org/docs/latest/api/session#event-spellcheck-dictionary-download-begin My guess is the spellcheck does not work for the languages we have already configured in Windows settings "Language & region." |
Preflight Checklist
Electron Version
12.0.4
What operating system are you using?
Windows
Operating System Version
Windows 10 1909
What arch are you using?
x64
Last Known Working Electron version
None
Expected Behavior
Expecting
require('electron').webFrame.isWordMisspelled('testt')
to returntrue
.Actual Behavior
require('electron').webFrame.isWordMisspelled('testt')
returnsfalse
.Testcase Gist URL
https://gist.github.com/lishid/53782e6e43f4bc431ac1fed3bff33c85
The text was updated successfully, but these errors were encountered: