Buri, using: Gaia: c8f14ad3950d59ba13d7639eff02d080060bb3ce Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/244e98241b2c BuildID 20131203004002 Version 26.0 ro.build.version.incremental=eng.archermind.20131114.105818 STR: 1. Import a set of > 5000 facebook contacts (to get meaningful scrolling real estate 2. Observe the attached movie - no Facebook icons or photos show at all at first until after scrolling stops.

I see the same issue when scrolling back up.

I don't know if this is a regression or not. It's certainly perf related, however. QA Wanted to see if this reproduces on 1.1 or 1.2.

Hi guys, in my opinion this is not a bug but the right behavior. In fact, we implement a lazy loading mechanism for the contact photos which basically releases the photo when they are not in the viewport and reloads them when the contact is again in the viewport. The consequence of this lazy loading mechanism is what you show in the attached video. I confirmed it with Francisco and Cristian but let's also ask Ben about it :-)

BTW, there is an issue in master (not in 1.2) which basically shows the "broken link ghost image" (so to call it) when scrolling (see the file attached). This is due to having the src attribute set to ''. The solution is to delete the src attribute or to include a '' alt one. I have filled a new bug to track it (bug 946260).

Facebook profile images do not display beside the associated contact until the user has stopped scrolling in both v1.1 and v1.2. Once scrolling has ceased the images, as well as the Facebook logo, appear almost immediately. There are no broken image icons, only blank space until the image loads. It is not necessary to have over 5000 contacts to reproduce this effect; it was accomplished with a mere 115 Facebook contacts. 1.1 Environmental Variables: Device: Buri v1.1 COM RIL BuildID: 20131206041202 Gaia: 6ff3a607f873320d00cb036fa76117f6fadd010f Gecko: 05117f42088f Platform Version: 18.1 RIL Version: 01.01.00.019.281 Firmware Version: v1.2_20131115 1.2 Environmental Variables: Device: Buri v1.2 COM RIL BuildID: 20131206004002 Gaia: d48df33cbdae2063f12b09e3dca07ff7a2f2a3cc Gecko: fd0302696c57 Version: 26.0 Firmware Version: v1.2_20131115

Ups, it seems I forgot to include the need-info to Ben regarding comment 3 and everything which came after it :-) Thanks!

Yes, this is currently how its designed to work in order to keep our scrolling performance up. If its a priority for UX that images show immediately we could investigate rendering the image when the row comes on screen via the visibility_monitor. My naive initial attempt at implementing that approach, however, resulted in quite janky scrolling. So this would probably take some time to investigate.

Hi John, are you OK with Ben's explanation in comment 8? :-) If you are, please set the bug as RESOLVED - INVALID or WORKSFORME :-) Just not to leave bugs open :-) Thank you very much! (thought it would be kind of rude to do it myself :p )

gtorodelvalle - very sorry about the delay! If this is the intended behavior, then I'm OK with it. Marking as resolved WONTFIX if that's ok.