Steps to reproduce: 1.In“Dev Web Apps” navigate to an app with video content and press “OK”(“Enter” key on the keyboard). 2.Select icon for login/register and choose register. 3.Enter credential and press next. 4.Press back. Expected results: User should go back to first name. Actual results: Two text-fields are displayed with email and last name. Note/Issues: Environment: 2.5 Simulator. This issue is reproducing in -dev server. Video to this issue: https://www.dropbox.com/s/podqpmcybwvfi3f/Back-2fileds.mp4?dl=0

Confirmed this bug on the 2.1 TV. This is certainly a bug we should address. More info: Issue occurs on Future Today sites (example iFood) There is a two step login process (email and PW) needed here Using Mozilla provided keyboard, the user is inclined to press blue "done" after entering email. (this causes the form to attempt to submit before PW is entered, then fail, then the site reloads the landing page with no error msg provided to user) Happy path is to press the "minimize keyboard" button then use highlight nav to enter using the provided keyboard from Future Today.

@ HK - can you investigate this issue?

> This is certainly a bug we should address. This doesn't seem to block the registration flow; what is the concern here to make it a blocker?

Attaching a pic of the issue that concerns me (blocker) I was only able to reproduce this issue for 10% of attempts STR: -Launch a Future Today app (ie iFood) -Navigate down until lock icon (login)is highlighted -Press ok -enter text for an email on large white keyboard -minimize large white keyboard -nav to “Next" on black keyboard using down arrow & then more dpad -Press Enter -Minimize large white keyboard (if it appears) -Use black keyboard to enter a PW -Press next to submit -Observe results

:evelyn: I want to recommend the developer to feature detect if the device has an on-screen keyboard; in which case the page should never show their own quirky keyboard input which conflicts with the native on-screen keyboard input. How would site detect support of on-screen keyboard input?

As I know, the system won't send any event to the content window to indicate there is a on-screen keyboard. However, for now we could assume the on-screen keyboard will always exist on FxOS when an input field gets focus(*). So, a possible solution is to detect UA string to know it's run on FxOS device. * This will change when we integrate hardware keyboard plug-in scenario. See bug 1110030 for more information.

Since web apps won't in 2.6 scope, this issue is not valid anymore after removing web apps from our build.