1074089 - [Messages][SMS] White rectangle appears on top of '3 dots' and 'new message'

Status: RESOLVED WORKSFORME

(Core :: Graphics: Layers, defect)

Description

[Eric Chang [:ericcc] [:echang]]

### STR
1. Have some SMS in it.,
2. Touch and slide on 'Settings' or 'New Message'

### Actual
http://youtu.be/hOSYZfQSNeA

### Reproduce rate 
50%

### Version
Gaia-Rev        13973ab50760d1e8bb773082163f0dff19d35a44
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-aurora/rev/6e317e075d04
Build-ID        20140928160204
Version         34.0a2
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20140928.193620
FW-Date         Sun Sep 28 19:36:31 EDT 2014
Bootloader      L1TC10011800

Comment 1

[Julien Wajsberg [:julienw]]

Looks like a Graphics issue.

Comment 2

[Julien Wajsberg [:julienw]]

Wondering if this can be related to bug 1063046 in some way.

Comment 3

[Joshua Mitchell (Inactive)]

Julien - Please review https://wiki.mozilla.org/B2G/QA/Triage#Summary_of_Keywords_and_Flags

 which states a bug has to be a blocker to request a window

Comment 4

[Julien Wajsberg [:julienw]]

Joshua,

as it's stated on the wiki, it's expensive to do a window. That's why it's extremely useful if the QA team can do it instead of the developer.

I'm fine if the request has lower priority. But I think the criteria "it needs to be a blocker" is counterproductive. This bug is probably not the place to discuss this though... where could this happen?

Comment 5

[Tony Chung [:tchung]]

hi Julien,  we can work on a backlog of qawanted requests, but probably during a window where the releases are winding down.   given most folks on qawanted responbilities is focusing on 2.1 blockers, its important that they prioritize those first, before getting to the backlog.

I would also not make this a mozilla QA request only, as qawanted is really open to anyone that has public builds and can help with validations.   In this particular bug, i do agree with joshua that we need to backlog the priority here, but we can have a public discussion on a plan and approach for tackling this long list when things die down.  But for now, the team operates of the qa requests page [1], so unless its on that list to prioritize, we will need a backlog to be added.

Lastly, i dont see why this can't be publically discussed in mozilla.dev.b2g and mozilla.dev.gaia.

there is some time between 2.1 CC and 2.2 sprint 1.   working through a backlog of these qawanted requests then is not out of the question.

[1] https://wiki.mozilla.org/B2G/QA/Triage#QA_Requests

Comment 6

[Tony Chung [:tchung]]

by the way, i was getting a square drawn around the camera icon when entering the lockscreen passcode.  it this related?   http://youtu.be/p3Q_RXC-UL4

Comment 7

[Julien Wajsberg [:julienw]]

I think it's unrelated, but I'm not sure.

Comment 8

[Chris Kreinbring [:CKreinbring]]

Unable to repro on today's Flame 2.2 or 2.1 with nightly (full flash) or engineering (shallow flash) builds.
Actual result:  Tapping then swiping away from the New Message or Settings button causes the button to return to the untapped state with no visual errors.

Flame 2.2 engineering
BuildID: 20141029054810
Gaia: a9a847920b51b79c4ad4ad339f0a005777a6228c
Gecko: c6989e473f97
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Flame 2.2 nightly
BuildID: 20141029040208
Gaia: 35e87ac4324f0f3abd93dcc70d61c9f37256a0f5
Gecko: 7e3c85754d32
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Flame 2.1 engineering
BuildID: 20141029082611
Gaia: 2099fb0df60548cf7d4afc367f5048622cc29b3e
Gecko: f02f3fbd0bb0
Platform Version: 34.0
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Flame 2.1 nightly
BuildID: 20141029001202
Gaia: eb0aab0f13c78c7ac378ad860e865c4b6eaf669f
Gecko: 318019f80a8e
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Platform Version: 34.0
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

--------------------------------------------------------------------------------------------------------

The bug did repro on a past Flame 2.1 engineering with shallow flash that was close to the reported build ID.
Actual result: Tapping then swiping away from the New Message or Settings button may cause the button to show a white square for a second before returning to the unselected state.

BuildID: 20140928144923
Gaia: 13973ab50760d1e8bb773082163f0dff19d35a44
Gecko: 6e317e075d04
Platform Version: 34.0a2
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Comment 9

[Joshua Mitchell (Inactive)]

Eric - can you repro this in the latest? It seems like this issue is fixed

Comment 10

[Eric Chang [:ericcc] [:echang]]

(In reply to Joshua Mitchell [:Joshua_M] from comment #9)
> Eric - can you repro this in the latest? It seems like this issue is fixed

No, I cannot reproduce this with latest v2.1 or master.

Comment 11

[Julien Wajsberg [:julienw]]

Thanks all!