Thanks for your report.

Does this happen with all Chinese/Japanese IMEs? I tried using "Pinyin - Simplified" and I don't see this - instead, "wo" is available for conversion. Which specific IME are you using?

Hi, thanks for the catch!

I tested the issue with
- Mac's default Japanese IME (Hiragana mode)
- Google Japanese IME (Hiragana mode)
- Mac's default Chinese IME (Simplified)
- Mac's default Chinese IME (Traditional)
and it reproduced with each of them.

A gif showing the issue using Mac's default Japanese IME is attached. Hope it helps.

Deleted: ime_confirm.gif 104 KB

	ime_confirm.gif 104 KB View Download

And by "Mac's default Chinese IME" I meant "Pinyin", yes.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I can reproduce on Mac, so marking Available. Is this bug Mac specific, or reproducible on other platforms as well?

Also reminds me of some work tapted did recently on IME, so I'm ccing him.

Tried testing the issue on chrome reported version# 71.0.3578.80 using Mac 10.14.0 with steps mentioned below:
1) Clicked on omnibox, typed Y and pressed Tab for youtube search
2) Enabled 'Pinyin' and typed 'wo', able to see 'wo' on the omnibox
Observations: Also tested the issue by changing the chrome language to japanese, seen same behaviour as mentioned above

@Reporter: Please find the attached screencast for your reference and let us know if we missed anything in reproducing the issue, provide your feedback on it which help in further triaging it in better way.

Thanks!

Deleted: 912921.mp4 2.9 MB

	912921.mp4 2.9 MB View Download

Hi!
I checked the video, and I can see the issue happen in there. So you do it correctly.
"wo" shouldn't show 哦 and so on on the suggestion list as they are letters for "o".（Instead, "wo" should show 我.）This means that "w" didn't get picked up for conversion.

I can reproduce the issue on my Win10 (Tested with Microsoft Japanese IME) and Linux Mint (Tested with Mozc). Chrome 71.0.3578.80 (Official build 64bit) on both.
So I believe it's a cross-platform issue.

Duplicate of issue 896962.

Thanks for spotting the similarity innaterebel@.  Marking as duplicate.