CEF Forum

As well as showing my frustration at my inability to activate the spell check. I want to share that it has already been solved and although it may be painful for me to accept how stupid I was, I am going to say it:
The solution given to deactivate the WinUseBrowserSpellChecker option is correct, if it works, the problem is that I was deactivating it wrong, since I did this:

Code: Select all

command_line->AppendSwitch("-disable-features=WinUseBrowserSpellChecker");

Should I have done this:

Code: Select all

command_line->AppendSwitchWithValue("-disable-features", "WinUseBrowserSpellChecker");

And it was amaitland that made me notice it.
Thank you all for your prompt response to my request for help.

The feature is disabled by default with https://bitbucket.org/chromiumembedded/ ... quests/415

Now that the alloy bootstrap is dead I'm back to a non-working spell check on Windows using the chrome runtime. Our app on the alloy bootstrap put spelling suggestions into the context menu with no additional action by me. Now with the chrome runtime I get the red underline but "No spelling suggestions" in the context menu. Looking at the params->GetDictionarySuggestions() there are no suggestions to put into the context menu manually. How do I get the suggestions back in there? Our Mac version of the app does put suggestions into the context menu. I've been unable to figure out how to get the cefsimple test app to show suggestions... it has a spell checker menu item in there but only to configure languages.

Thoughts on this?

Gotta say, this whole "swap runtimes in two versions, it'll be fine" thing is causing me more grief than I can express. Just had another issue pop up with notification interactions I'm trying to track down... worked in alloy, broken in chrome.

Spellchecking on Windows + Alloy was broken due to https://github.com/chromiumembedded/cef/issues/3055. This is unrelated to the Chrome bootstrap.

I'm truly confused. Spellchecking on Windows + Alloy (style) has been working with the "disable feature" thing mentioned in the thread above while using the alloy bootstrap. Spellchecking on Windows + Alloy (style) is now broken and the only change is the swap to the chrome bootstrap.

bjdupuis wrote:I'm truly confused. Spellchecking on Windows + Alloy (style) has been working with the "disable feature" thing mentioned in the thread above while using the alloy bootstrap. Spellchecking on Windows + Alloy (style) is now broken and the only change is the swap to the chrome bootstrap.

Functionality can change between Chromium versions. Are you talking about the same Chromium version in both cases?

magreenblatt wrote:

bjdupuis wrote:I'm truly confused. Spellchecking on Windows + Alloy (style) has been working with the "disable feature" thing mentioned in the thread above while using the alloy bootstrap. Spellchecking on Windows + Alloy (style) is now broken and the only change is the swap to the chrome bootstrap.

Functionality can change between Chromium versions. Are you talking about the same Chromium version in both cases?

Well, alrighty. I backloaded everything back onto a CEF version that supports alloy, 126.2.9, and tried again. The only change between these two build/runs is changing settings.chrome_runtime from false to true... when false and therefore using alloy runtime, I get suggestions. When true and therefore using chrome runtime I get no suggestions. So it doesn't seem like anything to do with functionality changes in Chromium versions but rather a difference in running under the chrome bootstrap.

I backloaded everything back onto a CEF version that supports alloy, 126.2.9, and tried again. The only change between these two build/runs is changing settings.chrome_runtime from false to true... when false and therefore using alloy runtime, I get suggestions. When true and therefore using chrome runtime I get no suggestions. So it doesn't seem like anything to do with functionality changes in Chromium versions but rather a difference in running under the chrome bootstrap.

Thanks, that's clear.

magreenblatt wrote:Thanks, that's clear.

Are there any next steps I need to take?