1356549 - Custom Tab:: forms are not focused

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: General, defect, P1)

Description

[Sorina Florean [:sflorean]]

Environment: 
Device: HTC (Android 7.0), Huawei MediaPad M2 (Android 5.1.1);
Build: Nightly 55.0a1 (2017-04-14);

Steps to reproduce:
1. Launch CustomTabsActivity opening the link https://goo.gl/c7sP0s;
2. Tap on last field;
3. Type some text.

Expected result:
The field tapped is focused and user can insert/write characters.

Actual result:
The field is not focused and is overlapped with the keyboard.

Notes:
Please check the video: https://youtu.be/iVkLUj7BQ2c.

Comment 1

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Somehow this link no longer works.
BTW, Jim, from the video is looks like a platform issue. Mind to take a look?

Comment 2

[Sorina Florean [:sflorean]]

The links: 
1. http://research.coolfields.co.uk/at-demo/form-examples-date.html
2. https://var.mpopp.net/bdemo/forms.php

Comment 3

[(inactive) Jim Chen [:jchen] [:darchons]]

Seems like the field _is_ focused right? Because you can still type in it; only it's covered by the keyboard.

I think we should set whatever flag that tells Android to resize our window when the keyboard displays, rather than have the keyboard show on top of the window.

Comment 4

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Setting P1 for the usability.

Comment 5

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

as per testing by Julian and myself, on Nexus5 and Pixel XL respectively, couldn't reproduce.

Comment 6

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Could you try reproduce again?

Comment 7

[Sorina Florean [:sflorean]]

Hi, tested and couldn't reproduce on latest Nightly. The form is focused, not covered by keyboard and I can see what I type. Device: Nexus 6 (Android 7.0.) and Huawei Honor (Android 5.1.1).

Comment 8

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

yes. I think it's somehow fixed by other patches.
we can resolve worksforme now?

Comment 9

[Sorina Florean [:sflorean]]

Yes, I will close this bug as worksforme, since the issue is not reproducible.