bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.

[Lockscreen] When Lockscreen is disabled Keyboard will disappear after selecting Rocketbar and tapping Power button twice.



Firefox OS
3 years ago
21 days ago


(Reporter: Johnt, Unassigned)


Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v2.1 affected, b2g-v2.2 unaffected)


(Whiteboard: [2.6-Daily-Testing][Spark][2.1-exploratory-3], URL)


(1 attachment)



3 years ago
Created attachment 8515182 [details]

Description: After the user has disabled Lockscreen and searches the Rocketbar the keyboard will appear. If the power button is tapped once to turn screen off and then once again to enable the screen the keyboard will disappear but the rocketbar will still be selected.

Repro Steps:
1) Update a Flame device to BuildID: 20141031001201
2) From settings disable the Lockscreen
3) From Homescreen scroll down a bit so that you are not at the top of the Homescreen.
4) Tap the Rocketbar at the top of the screen.
5) Press Power Button Twice.
6) Observe that the keyboard has now disappeared yet Rocketbar is still selected.

Keyboard disappear while Rocketbar is still selected.

It is expected that the Rocketbar will still be selected with the Keyboard still appearing.

Notes: The rocketbar and keyboard will no longer be selected if the Lockscreen is enabled

Flame 2.1 
Device: Flame 2.1 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141031001201
Gaia: f89c7b12c36572262c9ea76058694a139b1a8634
Gecko: 50d48f8a04c7
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 34.0 (2.1)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Repro frequency: 3/4
See attached: Logcat & Video
Video: https://www.youtube.com/watch?edit=vd&v=N3CW8VfEz0c

Comment 1

3 years ago
This issues does NOT occur on the Flame 2.2 KK (319mb) and on the Flame 2.0 KK (319mb)

Result: For the 2.2 the Keyboard displays successfully when searching Rocketbar and then powering the screen off and on. On the 2.0 however I am unable to bring up the Rocketbar from the Homescreen.

Flame 2.2

Device: Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141031061804
Gaia: a07994714f0552f89801d6097982308d8b0a1ee1
Gecko: 6bd2071b373f
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 36.0a1 (2.2)
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Flame 2.0

Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141031000201
Gaia: 7b8df9941700c1f6d6d51ff464f0c8ae32008cd2
Gecko: 82a6ed695964
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 32.0 (2.0)
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
striking regression tag - rocketbar from homescreen not implemented in 2.0 so this can't be a regression of that feature but a state of incomplete implementation. 

NI to Homescreen / Rocketbar owner for Nom decision
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
status-b2g-v2.0M: unaffected → ---
Flags: needinfo?(jmitchell) → needinfo?(mozillamarcia.knous)
Keywords: regression
This seems to me to be a pretty minor issue. Also the video is very glary and makes it difficult to see the actual issue.
Flags: needinfo?(mozillamarcia.knous)

Comment 4

2 years ago
Still seeing this issue occur on Aries Master. Updated the video representing the issue. 
Video: https://youtu.be/F3GdpVn30VY

Environmental Variables:
Device: Aries 2.6 Kk
BuildID: 20151202153750
Gaia: 719d89803fd1809bb1132e564a6d0c255963d4b7
Gecko: a0897ec629f90951e685f42eefecea8437481ecb
Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56
Version: 45.0a1 (2.6) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0
Flags: needinfo?(jmercado)


2 years ago
Whiteboard: [2.1-exploratory-3] → [2.6-Daily-Testing][Spark][2.1-exploratory-3]
Flags: needinfo?(jmercado)

Comment 5

21 days ago
Firefox OS is not being worked on
Last Resolved: 21 days ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.