1127048 - [Clock] After interacting with a Timer alarm notification and returning to the clock app the active tab will show as the previous selection even though the current active tab is now the Timer tab.

Status: RESOLVED DUPLICATE of bug 987834

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

Description

[Joshua Mitchell (Inactive)]

Attachment: logcat_20150128_1310.txt

Description:
When in the clock app there are 3 different tabs: Alarm, Timer and Stopwatch. The active tab is shown as being highlighted with blue text and underlined with a blue bar. When a Timer alarm goes off, and the user returns to the clock app the app will automatically shift to the Timer tab but the previously selected tab (Alarm or Stopwatch) will remain highlighted in blue.

Repro Steps:
1) Update a Flame to 20150128010234
2) Launch the clock app
3) Select the Timer tab
4) Set the time for 1 minute and select start
5) Select either the Alarm or Stopwatch tab
6) Allow time to expire and alarm to go off; dismiss it

Actual:
The app shifts to the Timer tab but the previously selected tab keeps the highlighting. 
This occurs even if putting the clock app in the background and returning to it

Expected:
If the active tab has switched, the blue highlighting will change to reflect that switch. 

Environmental Variables:
Device: Flame 3.0
Build ID: 20150128010234
Gaia: 1d53fb07984298253aad64bfa4236b7167ee3d4d
Gecko: b2b10231606b
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 38.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

Repro frequency: 8/8
See attached: logcat
-----------------------------------------------------------------------

This issue also occurs on Flame 2.2 (v18d-1), Flame 2.2 (v18d), Flame 2.1 (v18d-1) and Flame 2.0 (v18d-1)

evice: Flame 2.2 (KK - Nightly - Full Flash)
Build ID: 20150128002506
Gaia: cd42b034fd2825c3675ace3a67f5775eb61c2d60
Gecko: d824c65a6a2b
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 37.0a2 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Device: Flame 2.2 (KK - Nightly - Full-Flashed)
Build ID: 20150128002506
Gaia: cd42b034fd2825c3675ace3a67f5775eb61c2d60
Gecko: d824c65a6a2b
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 37.0a2 (2.2)
Firmware Version: v18d
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Device: Flame 2.1 (KK - Nightly - Full-Flashed)
Device: Flame 2.1
Build ID: 20150128001258
Gaia: d98bbe9d2bfdb53e80dc1ab1572bd05938a85526
Gecko: c694578ff69e
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 34.0 (2.1)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Device: Flame 2.0 (KK - Nightly - Full-Flashed)
Build ID: 20150128000201
Gaia: 2989f2b2bd12fcc0e9c017d2db766e76a55873b8
Gecko: 5bf8087572c3
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 32.0 (2.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 1

[Peter Bylenga [:PBylenga]]

I think this is the same as bug 987834.