1126777 - [Contacts] Can't scroll anymore once all contacts are loaded

Status: RESOLVED WORKSFORME

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

Description

[Julien Wajsberg [:julienw] (PTO -> Aug 14)]

STR:
1. have more than 1 page of contacts
2. launch the Contacts app
3. wait some seconds until all contacts app are loaded
4. try to scroll down

=> it doesn't work.

We can scroll while the contacts are loading. We can also scroll using the letters on the right.

qawanted for branch checks

Comment 1

[Julien Wajsberg [:julienw] (PTO -> Aug 14)]

The issue happens with the reference workloads too.

Comment 2

[Clément Lefèvre]

Strangely, clocking to add a contact then canceling this contact addition looks like a "strange workaround" but is fixing the issue. This probably change some status even if no real contact addition is done.

Comment 3

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

I cannot get this to occur on the latest working builds in both tinderbox and nightly.  I did repro it on yesterdays nightly though.  Julien can you still reproduce on today's build?  Removing the regression window tag for now, but if you can please readd it and someone else will check into this.

Issue does NOT occur

Tinderbox Engineering build
Environmental Variables:
Device: Flame 3.0
BuildID: 20150128120131
Gaia: 782d371263911a526870263bffcb419b52c7c88a
Gecko: 1daa622bbe42
Version: 38.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

Daily User build
Environmental Variables:
Device: Flame 3.0
BuildID: 20150129010239
Gaia: 9d2378a9ef092ab1fc15c3a9f7fc4171aab59d57
Gecko: 6bfc0e1c4b29
Version: 38.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

DOES occur

Environmental Variables:
Daily user build
Environmental Variables:
Device: Flame 3.0
BuildID: 20150128010234
Gaia: 1d53fb07984298253aad64bfa4236b7167ee3d4d
Gecko: b2b10231606b
Version: 38.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

Comment 4

[Julien Wajsberg [:julienw] (PTO -> Aug 14)]

Yes, looks like it's fixed !

Is it worth finding the bug that fixed the issue?