1491750 - Urlbar popup/panel remains open after Korean characters entered

Status: RESOLVED WORKSFORME

(Firefox :: Address Bar, defect, P3)

Description

[wernicke14]

Attachment: 2018-09-17 15.09.08.gif

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:63.0) Gecko/20100101 Firefox/63.0
Build ID: 20180913141435

Steps to reproduce:

I entered a string ending in Hangul in the address bar.

Tested in Firefox Nightly 64.0a1, macOS 10.13.6


Actual results:

The Suggestion UI remains after the page load.


Expected results:

The suggestion UI should be disappeared.

Comment 1

[Drew Willcoxon :adw]

Could you please describe in more detail the steps you are following, including how you are using your IME -- what keys you are pressing and when, what mouse clicks you're making?  This probably has to do with how autocomplete handles IME composition, but we need more info.  I can't reproduce the problem using macOS's Japanese IME.

Comment 2

[wernicke14]

I'm using macOS' Korean IME with 2-Set Korean input source.

Whatever the key I pressed, This problem happens. However, if the input character ends in the alphabet, there is no problem even if Korean characters are input.

The Problem occurs whether I click the Address bar or not. (As you know, when you open a new window with a shortcut, you don't have to click the mouse because the cursor is automatically placed in the address bar)

So, Here are steps I am following:

1. Click the address bar of an already open window. Or, Just press cmd + t, the new tab shortcut.
2. Press any keys and last input should be a Korean character.
3. Press the Enter Key.

Comment 3

[Drew Willcoxon :adw]

OK, thank you.  I can reproduce the problem using the Korean IME.  It looks like the whole popup remains open, but only the search buttons are present -- no listbox results.

Have you noticed the Firefox version where this started happening?  Is it Nightly only?

Comment 4

[wernicke14]

I don't remember exactly but maybe It started from 62 or 61.
My main browser is Developer Edition. So, It is pretty sure this happening on 63.

I don't think this is important, Just FYI, There is still the bug after macOS updating. (10.13 -> 10.14)
Thanks for your help.

Comment 5

[Marco Bonardo [:mak] (Away Apr 25 - May 5)]

This seems to be working correctly now, please feel free to reopen if you can still reproduce.