1106611 - [Email] Some already-painted DOM elements are repainted as black boxes at card animation completion then repainted correctly. On New Account Password page.

Status: RESOLVED DUPLICATE of bug 1113435

(Core :: Graphics, defect)

Description

[John Thomas [:Johnt]]

Description:
If the user navigates to the New Account page some black boxes appear when the hit boxes are rendered. 

Repro Steps:
1) Update a Flame to 20141126000203
2) Launch Email App
3) Enter Name and valid Email address.
4) Select Next
5) Observe rendering behaviour.

Actual:
Password hitbox has a black box rendering briefly.

Expected:
It is expected no rendering issues will occur. 

Flame 2.2

Environmental Variables:
Device: Flame 2.2 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141201040205
Gaia: 39214fb22c203e8849aaa1c27b773eeb73212921
Gecko: 08be3008650f
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 37.0a1 (Unknown)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Repro frequency: 100%
See attached: Video & Logcat
Video: https://www.youtube.com/watch?v=75blKRbY1cU

Comment 1

[John Thomas [:Johnt]]

This issue does NOT occur on the Flame 2.1 kk Shallow Flash (319mb) 

Result: For the 2.1 no blackbox appears when the password hitbox is displayed. As for the 2.0 the password page is already located on the previous along with the Name and Email address. I did not mark the flags for the 2.0 because of this layout.

 Flame 2.1

Device: Flame 2.1 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141201001201
Gaia: ccb49abe412c978a4045f0c75abff534372716c4
Gecko: 18fb67530b22
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Comment 2

[John Thomas [:Johnt]]

Attachment: logcat_20141201_1056.txt

Comment 3

[Andrew Sutherland [:asuth] (he/him)]

Moving to graphics for duping, etc.

Comment 4

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

[Blocking Requested - why for this release]:

The black boxes are very easy to see and this bug occurs when logging in with VALID log in info. This is also a regression. Nominating to block 2.2

Comment 5

[Pi Wei Cheng [:piwei] (inactive)]

Issue seems to only occur with an outlook account. It doesn't occur with a gmail account because it brings user to a different password entering screen. I haven't tested with other email accounts.

Working on getting the window now.

Comment 6

[Pi Wei Cheng [:piwei] (inactive)]

mozilla-inbound regression window:

Last Working Environmental Variables:
Device: Flame
BuildID: 20141129095244
Gaia: 7119da7a86cd803840678ca3a6067e5622adc481
Gecko: ba93c0eb3cf7
Version: 37.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

First Broken Environmental Variables:
Device: Flame
BuildID: 20141129104444
Gaia: 7119da7a86cd803840678ca3a6067e5622adc481
Gecko: 756000f8f25c
Version: 37.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Gaia is the same so it's a Gecko issue.

Gecko pushlog:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=ba93c0eb3cf7&tochange=756000f8f25c

Caused by Bug 1097941.

Comment 7

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

Broken by bug 1097941 - Benoit can you please take a look.

Comment 8

[Benoit Girard (:BenWa)]

Attachment: Tiled layer with a holes in it for the elements

Alright well the layer tree sent to the compositor is invalid.

Comment 10

[Tony Chung [:tchung]]

This reproduces on Settings App as well.  (Search, Homescreen, Notifications...)

See video: http://youtu.be/zl0KyKBRtw4

Comment 11

[Jeremiah Lee]

Issue can be seen when opening an email from inbox in Email app as well. On Flame 2.2.

Comment 12

[Benoit Girard (:BenWa)]

I'm waiting for inbound to land bug 1112332.

Comment 13

[Benoit Girard (:BenWa)]

This appears to be a culling issue, not a paint heuristics problem.

Comment 14

[Kartikaya Gupta (email:[e-mail])]

This appears to be fixed on the latest nightly, guessing it was fixed by bug 1113435 if it's culling.