Created attachment 8503363 [details] logcat_NoNumberOnUtilityTray.txt Description: On the utility tray, there is no number counter for "Notifications" string. The number of notifications is not displayed. Pre-requisite: Have at least 1 new notification. Repro Steps: 1) Update a Flame to Build ID: 20141010000201. 2) Pull down the utility tray. 3) Observe the top of the screen. Actual: No number before "Notifications" string. Expected: Number of Notifications is displayed before "Notifications" string. Flame 2.1 KK (319mb) (Full Flash) Environmental Variables: Device: Flame 2.1 BuildID: 20141010000201 Gaia: bc8eb493311c58f1f311a56b8b645b52bfbd2f71 Gecko: 72c13d8631ff Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 34.0a2 (2.1) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Repro frequency: 100% See attached: logcat, screenshot
This issue does NOT reproduce on Flame 2.2: Flame 2.2 Master KK (319mb) (Full Flash) Device: Flame 2.2 BuildID: 20141010040202 Gaia: 1036b544b7e102592bd9fab95cd9317329ac1293 Gecko: 50b689feab5f Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 35.0a1 (2.2) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 Number of Notifications is displayed before the "Notifications" string. =============================================== This issue involves the new deign elements for utility tray affecting 2.1. This feature does not exist on Flame 2.0: Flame 2.0 KK (319mb) (Full Flash) Environmental Variables: Device: Flame 2.0 Build ID: 20141010000201 Gaia: 9791940d5093c37336dcd85f7e66e9a8445a218e Gecko: 00d3c843aeec Version: 32.0 (2.0) Firmware Version: V180 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
It's probably too late to uplift a fix for this, and it's not terrible UX in any case. cc'ing Rob, but marking as won't fix.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
You need to log in before you can comment on or make changes to this bug.