1161119 - [SMS] The notification bar is present (and overlaps header) when viewing an image immediately after sending it

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::System::Status bar, Utility tray, Notification, defect)

Description

[Joshua Mitchell (Inactive)]

Attachment: logcat_20150504_0929.txt

Description:
After sending a MMS, if the user taps on the picture that they just sent then the notification bar icons will appear in the preview, overlapping the header. This issue also occurs with other media such as video 
or media taken from the Camera. This issue is timing sensitive and repro's best if tapping on the image (to see the preview) immediately after sending it. 
This issue can also occur by locking and unlocking the device while on the picture preview.

Repro Steps:
1) Update a Flame to 20150504010202
2) Launch SMS app
3) Compose new message, add a recipient, attach a picture and send
4) Tap on the sent picture to access full-screen preview

Actual:
Notification bar icons are present and overlap header


Expected:
Notification bar icons do not appear on picture preview


Environmental Variables:
Device: Flame 3.0
Build ID: 20150504010202
Gaia: e18cce173840d6ff07fb6f1f0e0ffb58b99aab3e
Gecko: dc5f85980a82
Gonk: a9f3f8fb8b0844724de32426b7bcc4e6dc4fa2ed
Version: 40.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0


Repro frequency: 7/10

See attached: logcat video clip: http://youtu.be/9uS8842apLo

Comment 1

[Joshua Mitchell (Inactive)]

This issue does NOT reproduce in Flame KK 2.2

Actual Results: No notification icons appear on the full-screen preview

Device: Flame 2.2 (KK - Nidghtly - Full Flash - 319mem)
Build ID: 20150504002502
Gaia: 8d14361337e608c8cdf165ea5034db5eda23b618
Gecko: cb7cb6597c91
Gonk: a9f3f8fb8b0844724de32426b7bcc4e6dc4fa2ed
Version: 37.0 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Comment 2

[Julien Wajsberg [:julienw]]

[Blocking Requested - why for this release]:

Comment 3

[Yeojin Chung [:YeojinC]]

b2g-inbound Regression Window:

Last Working Device: Flame 3.0
BuildID: 20150417033338
Gaia: ae7527a6e6892b92b67925b3c892e03c6d920ff3
Gecko: 136a62df9e18
Version: 40.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0

First Broken Environmental Variables:
Device: Flame 3.0
BuildID: 20150417035137
Gaia: 3b38ebb44d3313bd39e7378b21d004c6b84eecf2
Gecko: 86970b32c0c8
Version: 40.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0

Last Working Gaia First Broken Gecko: Issue does NOT reproduce 
Gaia: ae7527a6e6892b92b67925b3c892e03c6d920ff3
Gecko: 86970b32c0c8

First Broken Gaia Last Working Gecko: Issue DOES reproduce
Gaia: 3b38ebb44d3313bd39e7378b21d004c6b84eecf2
Gecko: 136a62df9e18

https://github.com/mozilla-b2g/gaia/compare/ae7527a6e6892b92b67925b3c892e03c6d920ff3...3b38ebb44d3313bd39e7378b21d004c6b84eecf2

Caused by bug 1152718

Comment 4

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

Guillaume, can you take a look at this please? This might have been caused by the work done for bug 1152718.

Comment 5

[Julien Wajsberg [:julienw]]

mmm bug 1152718 landed in v2.2 -- therefore it's quite strange this bug doesn't happen in v2.2?

Comment 6

[Guillaume Marty [:gmarty]]

I can't replicate this bug on today's master build, even if I try the locking/unlocking method.

Can you try again and see if you still reproduce it?

Comment 7

[Joshua Mitchell (Inactive)]

try as we might, we are not able to reproduce this issue anymore

Environmental Variables:
Device: Flame 3.0
Build ID: 20150511010202
Gaia: 6089234ace8b294a8feef064387604bae16254e3
Gecko: d8420a541d1c
Gonk: a9f3f8fb8b0844724de32426b7bcc4e6dc4fa2ed
Version: 40.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0