1593320 - Fennec/Fenix do not bring up virtual keyboard a testcase, Chrome does

Status: RESOLVED DUPLICATE of bug 1658948

(GeckoView :: IME, defect, P2)

Description

[Thomas Wisniewski [:twisniewski]]

Attachment: testcase.html

In the attached testcase, Chrome still brings up the virtual keyboard when tapping on the overlay covering the textarea, despite the mousedown event being default-prevented. Firefox does not.

Chrome seems to be bringing up the keyboard because the textarea is already focused, regardless of whether the muosedown is canceled (if I remove the focus() call from the testcase, Chrome also eats the event without bringing up the keyboard).

Note that I'm not sure if the same behavior will be present on desktop editions of the browser with touchscreens and virtual keyboards, so it might be Android-specific.

Whether Chrome's behavior is reasonable or not, it may be desirable to users, as per the related webcompat issue.

Comment 1

[Olli Pettay [:smaug][[e-mail]](vacation until Nov 16)]

(not sure about the right component. but at least not DOM Events)

Comment 2

[Chris Peterson [:cpeterson]]

This could be a GV IME issue.

Comment 3

[Makoto Kato [:m_kato]]

Hmm, our implementation is that nsIWidget::SetInputContext shows VKB. But SetInputContext isn't called even if tapping textarea on sample HTML. So I guess that this may occur on Windows's VKB for tablet mode.

Isn't nsFocusManager::Focus called on this HTML?

Comment 4

[Makoto Kato [:m_kato]]

Nakano-san, do we have any change that IMEStateManater calls SetInputContext on this test case?

Comment 5

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

Hmm, I have no idea. It should be called from EditorEventListener::MouseClick() via IMEStateManager::OnClickInEditor(). I guess the changes for Fission must not affect this path.

Comment 6

[Makoto Kato [:m_kato]]

I am working similar issue on another bug.

Comment 7

[Chris Peterson [:cpeterson]]

Moving some keyboard bugs to the new GeckoView::IME component.