1394112 - [TSF] Google Japanese Input's English mode doesn't work on Firefox 55, only on location bar

Status: NEW

(Core :: DOM: UI Events & Focus Handling, defect, P5)

Description

[Kohei Yoshino]

From this Twitter thread with video: https://mobile.twitter.com/mozillajp/status/901451545233027072

Bug 1390097 solved an IME issue in Firefox 55, but in this case:

* Firefox 55.0.3 (64-bit) on Windows 10
* No multiple profiles or -no-remote command line option involved
* Reproduces with Safe Mode, on multiple devices
* No problem when switching input mode with the Hankaku/Zenkaku (半角/全角) key
* Only the first character is inserted when switching to the Eisuu (English/Number) input mode with the Eisuu (英数) key
* Then Backspace nor Escape key doesn't work, but hitting the Eisuu key again reverts to the previous state
* This bug only happens on the Location bar; no problem with the Search bar and other text areas on the web

Comment 1

[Kohei Yoshino]

[Tracking Requested - why for this release]: A regression from Firefox 55, and this is apparently different from Bug 1390097.

Comment 2

[Makoto Kato [:m_kato]]

Koshino-san, could you reproduce this?  I cannot.  This might be table-mode since we set input scope.

Comment 3

[Kohei Yoshino]

I don't have a JIS keyboard, unfortunately.

Comment 4

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

(In reply to Kohei Yoshino [:kohei] from comment #3)
> I don't have a JIS keyboard, unfortunately.

Perhaps, you can test it even without specific physical keyboard since Google Japanese Input has key configuration UI.

Comment 5

[Makoto Kato [:m_kato]]

Attachment: tsf.log

Comment 6

[Makoto Kato [:m_kato]]

That log is typing [a] and [b] multiple times, but composition text is 'a' only.

Comment 7

[Liz Henry (:lizzard) (relman/hg->git project)]

Tracking for 56 - if you land a fix,  please ask for uplift to beta and probably to release also.

Comment 8

[Mike Taylor [:miketaylr]]

Makoto-san, just to be clear, does Comment #6 mean you can reproduce?

Comment 9

[Makoto Kato [:m_kato]]

(In reply to Mike Taylor [:miketaylr] from comment #8)
> Makoto-san, just to be clear, does Comment #6 mean you can reproduce?

Yes, I can reproduce this, but this bug occurs on Firefox 52+

Comment 10

[Jim Mathies [:jimm]]

Hey Masayuki, should we track this? Trying to determine how serious this is for 57.

Comment 11

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

According to the report timing, I don't think that this is so important. However, for some Google Japanese Input users who use this way to turn input mode to English, this must be really annoying.

So, if we can fix, we should release the fix as soon as possible. But I don't give so high priority for this bug. If I'd have much time, I'd like to check this next week.

Comment 12

[Gerry Chang [:gchang]]

Mark 55/56 won't fix as we are 1 week from RC.

Comment 13

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Moving all open keyboard/IME handling bugs to DOM: UI Events & Focus Handling component.

Comment 14

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Oh, I forgot this, and still reproducible.

Comment 15

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Oh? I hit another bug, perhaps. I cannot reproduce this bug cleanly. How about you, makoto-san?

Comment 16

[Makoto Kato [:m_kato]]

(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900) from comment #15)

Oh? I hit another bug, perhaps. I cannot reproduce this bug cleanly. How about you, makoto-san?

I cannot reproduce this when using the latest Nightly. Also I will clean up the input scope code by bug 1618759 to support inputmode of current spec.