Spell check suggestion text is not available in ContextMenuRequested event

[q71114]

Description
CoreWebView2ContextMenuRequestedEventArgs.MenuItems for CoreWebView2.ContextMenuRequested event contain list of commands with spellcheck name but there's no way to get the actual suggestion text.

Version
SDK: 1.0.1189-prerelease
Runtime: 100.0.1185.29
Framework: WPF
OS: Win11

Repro Steps

1. Add event handler to CoreWebView2.ContextMenuRequested
2. Start the application
3. Right click on a misspelled word
4. There are spellcheck commands in CoreWebView2ContextMenuRequestedEventArgs.MenuItems but there's no suggestions available for any of them. Setting their CommandId as SelectedCommandId works properly as the misspelled word will be corrected.

Screenshots

Additional context
Without this information it's not possible for us to build a custom context menu with spell check suggestions.

AB#45525011

[champnic]

Thanks for the bug report @q71114 - I've added this to our backlog.

[SDev2022]

I am also facing same issue in release build 1.0.1185.39

[carlosbet]

Description
The problem still active on 1.0.1245.22 build.
And added to this bug, I do not open a new because I think this is a same issue. The simple fact of use Console.WriteLine to get feedback causes that suggestions never shown. For example:

for (int i = 0; i < e.MenuItems.Count; i++)
{
    Console.WriteLine($"{e.MenuItems[i].Name} -- {e.MenuItems[i].CommandId}");
    if (!acceptedCommandIds.Contains(e.MenuItems[i].CommandId))
    {
        e.MenuItems.RemoveAt(i);
        i -= 1;
    }
}

And now a curious behavior. If I remove Console.WriteLine, the first time that the context menu it's open, suggestions are not shown and message “getting suggestions” stay freeze, but then, on the following calls, all works fine and suggestions are shown. Even if in the first time the open menu has another kind (Page for example), the next times spell suggestions will work fine… Maybe some missing initialization?

Version
Runtime: 1.0.1245.22
Framework: NET 6.0 - WinForms
OS: Win10 x64

[MarkIngramUK]

@carlosbet , your "curious behaviour" sounds like it could be #3142

[srwei]

When right clicking for the context menu on the misspelled word text, what are you seeing? Are there blank strings in the menu items or is there the placeholder (i.e. "Getting suggestions")?

[RendijsSmukulis]

@srwei Following @q71114 's repro steps, we're seeing blank labels in the CoreWebView2ContextMenuRequestedEventArgs.MenuItems:

+++> Caught CoreWebView2ContextMenuRequestedEventArgs with menu items:
 +++> label: '', name: 'spellcheck', kind: 'Command'
 +++> label: '', name: 'spellcheck', kind: 'Command'
 +++> label: '', name: 'spellcheck', kind: 'Command'
 +++> label: '', name: 'other', kind: 'Separator'
 +++> label: 'Cu&t', name: 'cut', kind: 'Command'
 +++> label: '&Copy', name: 'copy', kind: 'Command'
 +++> label: '&Paste', name: 'paste', kind: 'Command'
 +++> label: 'P&aste as plain text', name: 'pasteAndMatchStyle', kind: 'Command'
 +++> label: '&Share', name: 'share', kind: 'Command'
 +++> label: '&Web capture', name: 'webCapture', kind: 'Command'
 +++> label: '', name: 'other', kind: 'Separator'
 +++> label: 'I&nspect', name: 'inspectElement', kind: 'Command'

Note that this is repro'd by handling CoreWebView2.ContextMenuRequested event, as per the original bug report.

[fvanheeswijk]

When can we expect this issue to be resolved? Without it we cannot fully integrate WebView2 in our application and this bug has been open for more than a year already...

[fvanheeswijk]

Has there been any news on this @champnic and @srwei? Spell checking still is a major issue and it seems like multiple users here are reporting these things, is a review of the spell checking API in the works?

[Flaflo]

I also would like to know the current state of this issue. @srwei

[pdolanjski]

The spell checking APIs are currently completely broken. Because of this bug a custom context menu cannot be used (since you're left with blank labels so the spelling options cannot be displayed for users), but even if you attempt to use a non-custom context menu, because of issue 3142 the spelling suggestions just never appear.
cc @nishitha-burman @liminzhu