1107306 - [Homescreen] Menu options do not highlight when tapped.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Homescreen, defect)

Description

[Seth Miko [:SMiko]]

Description: The Homescreen menu options do not highlight when pressed. If long pressed, they do highlight but do not function. 

Repro Steps:
1: Update a Flame to 20141203040207.
2: Long tap on the homescreen to invoke the homescreen menu.
3: Tap on any option on the menu. 

Actual: The menu options do not highlight when tapped. 

Expected: Menu options highlight when tapped. 

Device: Flame 2.2 (319mb/full flash)
BuildID: 20141203040207
Gaia: 725685831f5336cf007e36d9a812aad689604695
Gecko: 2c9781c3e9b5
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 37.0a1 (2.2) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Repro frequency: 5/5

Comment 1

[Seth Miko [:SMiko]]

This issue DOES repro on Flame 2.1(319mb/full flash)

Actual result: 
The menu options on the homescreen menu do NOT highlight.

Device: Flame 2.1
BuildID: 20141203001205
Gaia: dbaf3e31c9ba9c3436e074381744f2971e15c7bf
Gecko: ebce587d2194
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 34.0 (2.1) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Comment 2

[Peter Bylenga [:PBylenga]]

qawanted for branch checks.

Comment 3

[Cody Roesch [:croesch]]

Tested with Shallow Flash on 319mb using Engineering builds.

This bug repro's on Flame KK builds: Flame 2.2 KK, Flame 2.1 KK, Flame 2.0 KK, Flame v188-1 Base

Actual Results: Tapping to interact with home sceen buttons do not produce a button highlight. Long tapping produces highlight but no function.

Repro Rate: 10/10

Environmental Variables:
Device: Flame 2.2 KK
BuildID: 20141203164306
Gaia: 984e6d79aa799d2695f9ca132dfdc1665a56c019
Gecko: a9fc46355661
Version: 37.0a1 (2.2) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.1 KK
BuildID: 20141203065100
Gaia: 5655269098c7e82254e56933f1af05b4abe2a2f3
Gecko: 86608c9389b5
Version: 34.0 (2.1) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.0 KK
BuildID: 20141203093700
Gaia: 8d1e868864c8a8f1e037685f0656d1da70d08c06
Gecko: ff1100ba2ab8
Version: 32.0 (2.0) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame v188-1 Base
BuildID: 20141021162107
Gaia: 8c5c956ee6909408e29f375cc7d843a03d92f3d8
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 4

[Joshua Mitchell (Inactive)]

NI Homescreen owner for blocking decision. Notes: Not a regression

Comment 5

[KTucker [:KTucker][Inactive 3/4/2016]]

Not a regression and seems minor so not nominating to block on this.

Comment 6

[Parul Mathur [:pragmatic] - out of office - please ni? [:bajaj] instead]

:kgrandon, would you consider this to be a polish bug?

Comment 7

[Kevin Grandon :kgrandon]

I think this fits the definition of a polish bug in my view.

Comment 8

[Kevin Grandon :kgrandon]

Mass update: Resolve wontfix all issues with legacy homescreens.

As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.