Is there any more detailed repro steps or test cases?

I can't reproduce locally with Chrome Mac Canary 68.0.3433.0 with the two options enabled.

Tried typing editpad.org. When right-clicking on the misspelled words, the context menu shows suggestions as expected. When opening the spelling panel, the suggestions are also shown as expected.

Repro step:

Enable  "Ask Google for suggestions"
Type "icland is an icland" in a spellchecked textbox.

The first "icland" should have one suggestion - "Iceland". The second one should have also only one suggestion, "island". If you see more than one suggestion, or different suggestions, those are provided by the system spellcheck.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7cdf18f8b5ff707820ceb8c2e18ec3e5b75a9ad0

commit 7cdf18f8b5ff707820ceb8c2e18ec3e5b75a9ad0
Author: Rachel Blum <groby@chromium.org>
Date: Fri May 18 01:35:01 2018

[Spellcheck] Look up browser context directly.

Looking it up via the RenderProcessHost fails, because the identity
doesn't seem to attached to an RPH.

It's not entirely clear why, but it removes an unnecessary redirection either way, so here it is.

R=xiaochengh@chromium.org

Bug:  844126 
Change-Id: I487d47d974b0c6ad45e90bb669a5b34f0b076717
Reviewed-on: https://chromium-review.googlesource.com/1063117
Commit-Queue: Rachel Blum <groby@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559770}
[modify] https://crrev.com/7cdf18f8b5ff707820ceb8c2e18ec3e5b75a9ad0/chrome/browser/spellchecker/spell_check_host_chrome_impl_mac.cc

Able to reproduce the issue on chrome build without fix(68.0.3433.0)
Verified the fix on Mac 10.12.6 on Chrome version #68.0.3434.0 as per the comment#0 & 2
Attaching screen cast for reference.
Observed "The correct suggestions are seen"
Hence, the fix is working as expected.
Adding the verified label.

Thanks!

Deleted: 844126.mp4 1.9 MB

	844126.mp4 1.9 MB View Download

Do we have a date when this fix is rolling out to prod, please?

Fix landed in 68.0.3434.0 so it will be in the next stable release (End of July).

 Issue 843864  has been merged into this issue.