857929 - [TABLET] Scrolling msn.com page autocratically accesses the search-field

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[Paul Feher]

Aurora 22.0a2 (2013-04-02)
Devices: Asus Transformer TF101 (Android 4.0.3), Acer Iconia (Android 3.2), Samsung Galaxy Tab 2 (4.1.1)

Steps to Reproduce:

1. Load msn.com
2. Close the keyboard
3. Scroll the page.

Expected:
The search-field in not in the focus an you can scroll the page.

Actual:
When scrolling, the search-field is autocratically focused and the keyboard appears making the site content difficult to access.

Comment 1

[Aaron Train [:aaronmt]]

This works for me on my TF201, Nightly (04/04). On page-load the search box is auto-focused and the keyboard is invoked. On dismissal I dont see it ever invoked again: http://www.youtube.com/watch?v=-Z47-PZTpo4

WFM.

Comment 2

[Paul Feher]

Now the behaviour is even stranger, the keyboard appears and disappears by itself after scrolling the page. 
You might need to reload the page if it can't be reproduced this issue the first time.

Please see the video
http://youtu.be/qXR0CB5e4A8

Comment 3

[Kartikaya Gupta (email:[e-mail])]

I can repro comment 0 on my Galaxy Tab. It settles down after a little while though, unlike the video in comment 2. Still, this needs fixing.

Comment 4

[Kartikaya Gupta (email:[e-mail])]

Actually this appears to not be a bug. When the page loads, it puts focus in the search field at the top, so we pop up the keyboard. If you hide the keyboard and scroll down, it brings up this footer fixed-position bar with another search field and puts focus in that, so the keyboard appears again. The page hides the footer if either the search field at the top of the page or the bottom of page are visible, so in the video in comment 2 it oscillates between hidden and not hidden.

I think the only reasonable way to fix this on our end is to not show the keyboard by default if content puts focus in an input element, but that's a significant behaviour change that we may not want to do.

Otherwise bumping this to evangelism seems reasonable.

Comment 5

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.