1177908 - [Browser] Scrolling on Gmail password entering sign in page shows undesired effect over the avatar icon

Status: RESOLVED FIXED

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

Description

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

Attachment: logcat of issue

Description:
If user tries to sign in to their gmail account via Email app or via Browser, they will observe on the password entering page if they scroll up and down, the avatar icon shows an odd animation.

STR:
1) Open Email app and attempt to log in to a gmail account
2) On the page where it asks for password, scroll up and down on the page, and observe the avatar icon

Expected: Nothing weird should show on the avatar icon

Actual: The background of the avatar icon scrolls separately with the foreground icon.

Video of issue:
https://www.youtube.com/watch?v=a2vG60OLDHQ

Repro rate: 10/10. The same effect will show if user uses Browser and go to gmail.com to sign in.

Attaching a logcat.

Device: Flame (KK, full flashed, 319MB)
BuildID: 20150626010205
Gaia: 038e917076271d304b906a41b4de670e505c67ae
Gecko: bbc26cc168c7
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 41.0a1 (3.0 Master) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Comment 1

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

Flame 2.2 is unaffected. Scrolling on the mentioned page shows the avatar icon scrolling as a whole as opposed to on 3.0 it separates the icon into foreground and background and have different scrolling speeds.

Device: Flame 2.2
BuildID: 20150626002504
Gaia: 1f8981d7872e3c0053571c26fb3edaf401844d75
Gecko: 2f8b845e5fa3
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
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

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

Seems minor so not nominating to block on this but let's get a regression window anyway.

Comment 3

[Shally Li（leave from Mozilla）]

Mozilla-inbound Regression Window:

Last Working Environmental Variables:
Device: Flame Master
Build ID               20150609113306
Gaia Revision          31ef8deec7a04a988eb92309178b87cc0bde8220
Gaia Date              2015-06-08 14:48:40
Gecko Revision         https://hg.mozilla.org/integration/mozilla-inbound/rev/84001a367d36
Gecko Version          41.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150610.043331
Firmware Date          Wed Jun 10 04:33:42 EDT 2015
Bootloader             L1TC000118D0

First Broken Environmental Variables:
Device: Flame Master
Build ID               20150609121708
Gaia Revision          31ef8deec7a04a988eb92309178b87cc0bde8220
Gaia Date              2015-06-08 14:48:40
Gecko Revision         https://hg.mozilla.org/integration/mozilla-inbound/rev/dc07aa95d2c9
Gecko Version          41.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150610.043331
Firmware Date          Wed Jun 10 04:33:42 EDT 2015
Bootloader             L1TC000118D0

First Broken Gaia & Last Working Gecko - issue DOES NOT repro
Gaia Revision          31ef8deec7a04a988eb92309178b87cc0bde8220
Gecko Revision         https://hg.mozilla.org/integration/mozilla-inbound/rev/84001a367d36

First Broken Gecko & Last Working Gaia - issue DOES repro
Gaia Revision          31ef8deec7a04a988eb92309178b87cc0bde8220
Gecko Revision         https://hg.mozilla.org/integration/mozilla-inbound/rev/dc07aa95d2c9


Mozilla-inbound pushlog:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=84001a367d36&tochange=dc07aa95d2c9

Possibly caused by Bug 1153589.

Comment 4

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

Kartikaya, can you take a look at this please? This might have been caused by the landing for bug 1153589.

Comment 5

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

tn, so should I back out the containerless-root change for B2G?

Comment 6

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

I am no longer seeing this issue on Aries and Flame with today's builds.

Comment 7

[Timothy Nikkel (:tnikkel)]

There is a good chance that bug 1180899 fixed this. So let's mark this fixed. If you see the problem again please re-open.