Marco Zehe (:MarcoZ) Reporter
	Description • 10 years ago

STR:
1. Run B2G master on a Flame.
2. Turn on screen reader.
3. Go to Settings, Firefox Account.
4. Touch and double-tap Sign In Or Create Account.
5. In the sheet that appears, type your e-mail address.

Result: As soon as you hit the @ sign, focus gets lost from the text field, and keyboard disappears.

6. Touch the field again and double-tap to bring up keyboard.
7. Complete your e-mail address. Notice that at the period of .com, for example, the focus loss does not occur.

8. Hit Next.
9. Start entering password. Mine contains letters and numbers.
10. Tap, then double-tap the 12... button at the bottom left.

Expected: Keyboard layer should switch, and I should be able to continue typing.

Actual: Layer switches, at first screen reader also announces that, but then, focus gets redirected to the Close button at the top left.

11. Touch, then double-tap the password entry again.

Result: Keyboard comes up, but again with the letters. Back to step 10.

Other keyboard fields like the address bar on the home screen, or signing up for a WiFi network, don't exhibit this behavior when switching keyboard layers.

I suspect the switching to numbers would also already fail if tried in steps 4 and 5 above, on the page where the e-mail address is being entered.

it sounds like this particular login is done via a sort of an iframe. Others are not. Maybe that is a factor?

	Brogan Zumwalt [Inactive]
	Comment 1 • 10 years ago

Flame 2.1 is also affected

Actual Result: Following STR to step 5 the user is unable to enter any information into text field after double tapping to bring keyboard up. Long pressing any letter to highlight keyboard it is dismissed without any change to the text field. The enter email field is left highlighted.

Device: Flame 2.1 (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141113001200
Gaia: 569a299ca446f714cd98d5881cc058fd6f6e257b
Gecko: d188e92aa5a6
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

	Brogan Zumwalt [Inactive]
	Comment 2 • 10 years ago

Issue does NOT occur on Flame 2.0

Actual Results: User can enter email and password for FxA with Screen Reader enabled. The keyboard is never unexpectedly dismissed and user can switch from alphabet to symbols and numbers keyboard without difficulty.

Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash)
Build ID: 20141114000200
Gaia: 28991b28d54fc4ef8112c8fa678bf20f9faca8c8
Gecko: 62294be0fc98
Version: 32.0 (2.0)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

	Chris Kreinbring [:CKreinbring]
	Comment 3 • 10 years ago

Unable to get a full regression window due to the fact that both gaia/gecko swaps reproed the bug.  
One swap will show the keyboard for a second before reclosing the keyboard, preventing the user from entering their credentials.
The other swap will show the keyboard, but it will only accept the first letter entered and other letters will not show in the textbox.  The keyboard will accept more than one symbols and numbers.

Regression window
Last working
BuildID: 20140728114105
Gaia: 295967a0b824a355ae9d57fb08f3632ed2ad18dd
Gecko: 9df0fa90ab34
Platform Version: 34.0a1
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

First broken
BuildID: 20140728123640
Gaia: fadfafa17f5175203b8b9457bfb95e5816f54f58
Gecko: 75fe3b8f592c
Platform Version: 34.0a1
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

	Wesley Huang [:wesley_huang] (EPM) (NI me)
	Comment 4 • 9 years ago

[Blocking Requested - why for this release]:
triage: should block because it's function broken. ni to RM as 2.1 is CC.

	bhavana bajaj [:bajaj]
	Comment 5 • 9 years ago

looks like an ancient nomination, can QA confirm we are still hitting this issue given the last time we saw this was 3 months back?

	Yeojin Chung [:YeojinC]
	Comment 6 • 9 years ago

Unable to verify this issue as I encounter a crash on Flame Master and 2.2 when trying to enter the password. I filed a new bug 1132769, which needs to be fixed to verify the current bug.

Environmental Variables:
Device: Flame 3.0
BuildID: 20150212064620
Gaia: 2a2b008f9ae957fe19ad540d233d86b5c0b6829e
Gecko: 81f979b17fbd
Version: 38.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

Environmental Variables:
Device: Flame 2.2
BuildID: 20150212133255
Gaia: ab9029f2b203e2a36e8f81edd17fa5ff81c874b5
Gecko: b1d3839680fb
Version: 37.0a2 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

	KTucker [:KTucker][Inactive 3/4/2016]
	Comment 7 • 9 years ago

Let's leave qawanted to have QA check this issue once the crash has been resolved.

	Naoki Hirata :nhirata (please use needinfo instead of cc)
	Comment 8 • 9 years ago

Still blocked.  Turns out that the crash wasn't one of the crashers from yesterday.  We'll need the core team to look at that crash.

	Yeojin Chung [:YeojinC]
	Comment 9 • 9 years ago

Bug 1132769 does not occur on today's nightly Flame Master, and this issue did NOT reproduce.

Result: The user was able to log in without any keyboard issue.

Device: Flame Master (KK, 319mb, full flash)
Build ID: 20150224010314
Gaia: 31ac1cd7a029d5e46dd7c92537b5c973c5d9826e
Gecko: 368c62292249
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 39.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0
===========================================================

Unable to verify on Flame 2.2 and 2.1, as the issue mentioned in Bug 1132769, Comment 1 still occurs.

Device: Flame 2.2 (KK, 319mb, full flash)
Build ID: 20150224002637
Gaia: 8e98fe665f3821d10d4d982cbb14cbe5b94d0be5
Gecko: 2b70d9d62799
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 37.0 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Device: Flame 2.1 (KK, 319mb, shallow flash)
BuildID: 20150223194120
Gaia: 86af0ca427adad12c3109124f31bef2fd9614e47
Gecko: a275f2c05ca6
Version: 34.0 (2.1) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

	Josh Cheng [:josh]
	Comment 10 • 9 years ago

Hi YeoJin,
Could you please help to verify the bug again as bug 1132769 not happen anymore? Thanks!

	Yeojin Chung [:YeojinC]
	Comment 11 • 9 years ago

(In reply to Josh Cheng [:josh] from comment #10)
> Hi YeoJin,
> Could you please help to verify the bug again as bug 1132769 not happen
> anymore? Thanks!

There is another blocking issue, bug 1137906. This issue still reproduces on today's nightly Flame Master.

Device: Flame Master (KK, 319mb, full flash)
Build ID: 20150305010212
Gaia: eff3321ab4e65da3f906688ebb55ddf1e93d9452
Gecko: 56492f7244a9
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 39.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0

	Josh Cheng [:josh]
	Comment 12 • 9 years ago

Hi Yeojin,
Can you verify this on 2.1 as bug 1137906 is unaffect to 2.1?

This issue is now 2.1 nominated.

Thanks!

	Yeojin Chung [:YeojinC]
	Comment 13 • 9 years ago

(In reply to Josh Cheng [:josh] from comment #12)
> Hi Yeojin,
> Can you verify this on 2.1 as bug 1137906 is unaffect to 2.1?
> 
> This issue is now 2.1 nominated.
> 
> Thanks!

The issue has been a little different on 2.1.  The user is unable to type in the email field at all when trying to log in with FxA. As soon as the user presses any key from the keyboard, the keyboard collapses and the user is returned to the previous screen. 

Environmental Variables:
Device: Flame 2.1
BuildID: 20150311172419
Gaia: db751d9c200dce41cd03a61665746d245739a175
Gecko: 28ffee0d5b0c
Version: 34.0 (2.1) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

	Steven Yang [:styang]
	Comment 14 • 9 years ago

(In reply to Yeojin Chung [:YeojinC] from comment #13)
> (In reply to Josh Cheng [:josh] from comment #12)
> > Hi Yeojin,
> > Can you verify this on 2.1 as bug 1137906 is unaffect to 2.1?
> > 
> > This issue is now 2.1 nominated.
> > 
> > Thanks!
> 
> The issue has been a little different on 2.1.  The user is unable to type in
> the email field at all when trying to log in with FxA. As soon as the user
> presses any key from the keyboard, the keyboard collapses and the user is
> returned to the previous screen. 
> 
> Environmental Variables:
> Device: Flame 2.1
> BuildID: 20150311172419
> Gaia: db751d9c200dce41cd03a61665746d245739a175
> Gecko: 28ffee0d5b0c
> Version: 34.0 (2.1) 
> Firmware Version: v18D-1
> User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
would you please file another bug for this symptom? thanks.

	Yeojin Chung [:YeojinC]
	Comment 15 • 9 years ago

> would you please file another bug for this symptom? thanks.

Sure, I filed it under bug 1145251.

	Yeojin Chung [:YeojinC]
	Comment 16 • 9 years ago

I was able to log in successfully on Flame 2.2 and 3.0. 2.1 is still blocked by bug 1145251.

Environmental Variables:
Device: Flame 2.2
BuildID: 20150319082140
Gaia: a3ef5b1a792957c8b22bb3cdded97f21e5a8cc88
Gecko: 99f7aadda070
Version: 37.0 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Environmental Variables:
Device: Flame 3.0
BuildID: 20150319060239
Gaia: c39e15f631de80c69467fda0d4ea0bcda9e194ca
Gecko: cbd0efcd976c
Version: 39.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0

	Pi Wei Cheng [:piwei] (inactive)
	Comment 17 • 9 years ago

Bug 1145251 is still occurring on Flame 2.1. We stopped testing on 2.1 so I think this is as good as we we can ever get on this bug. We don't even have newest 2.1 builds. Removing qawanted.

Device: Flame 2.1
BuildID: 20150724001207 (<- this is the latest that we have)
Gaia: 9dba58d18006e921546cec62c76074ce81e16518
Gecko: 41e10c6740be
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 34.0 (2.1) 
Firmware Version: v18Dv4
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

	Eitan Isaacson [:eeejay]
	Comment 18 • 6 years ago

We no longer work or support Firefox OS, so I am resolving this bug as WONTFIX.