1875606 - The keyboard isn't displayed on DuckDuckGo Maps

Status: UNCONFIRMED

(GeckoView :: IME, defect)

Description

[csheany]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0

Steps to reproduce:

Open https://duckduckgo.com/?t=h_&q=maps&ia=web&iaxm=maps
Tap the input field

Actual results:

The keyboard flashes

Expected results:

The keyboard is displayed

Comment 1

[csheany]

Attachment: Screen_Recording_Firefox Nightly.mp4

Comment 2

[csheany]

Would you mind taking a look?

Comment 3

[Makoto Kato [:m_kato]]

(In reply to csheany from comment #2)

Would you mind taking a look?

What your device (tablet?) ? I cannot reproduce this on Pixel 6a with Firefox Nightly.

Comment 4

[Makoto Kato [:m_kato]]

Although csheany's account is disabled, when looking other bugs, it seems to be tablet device. Galaxy tab?

Correct step is the following

STEP

1. Enable desktop site mode
2. Browser https://duckduckgo.com/?t=h_&q=maps&ia=web&iaxm=maps
3. Tab input field

Result

Lost focus of input field. Then keyboard is disappeared. When using Chrome with desktop site mode, focus is kept.

We need to debug DuckDuckGo content script why (I guess that they use event handler for touchstart and focus event). This may be WebCompat issue.

Comment 5

[Makoto Kato [:m_kato]]

(I guess that Chrome/Android doesn't fire resize event when showing VKB, so this won't occur)

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:m_kato, could you have a look please?

For more information, please visit BugBot documentation.

Comment 7

[Brian Birtles (:birtles)]

Adding Hiro to CC because it will be interesting to see if the virtual keyboard work fixes this if it means we stop firing a resize event when the VKB shows.

Comment 8

[Hiroyuki Ikezoe (:hiro)]

It's hard to tell without any diagnosis. Even if the site does something on a window.onresize event handler, this bug will not be automatically fixed by implementing interactive-widget (bug 1831649), since we will keep our current behavior by default for the backward compatibility, i.e. the window gets resized. Once after we implemented interactive-widget and the site specified interactive-widget=resizes-visual, this bug gets resolved.