Bugzilla

The broken rendering goes away pretty quickly for me in opt builds (e.g. Nightly) but it's still noticeable.

It lasts **many seconds** in a local enable-debug/disable-optimize build -- here's a screencast showing that, where we've got the broken rendering from t=0:27 to t=0:37 (ten full seconds).

I'm guessing (but haven't yet confirmed) that the limiting factor here (on when we switch from bad to good rendering) is whether we've gotten the new-tab-tile data back from Firefox's server that provides that.  If that is indeed true, then I would imagine that folks on slow connections might see this broken rendering for many seconds even in optimized official builds (looking something like this screencast).

The broken rendering goes away pretty quickly for me in official builds (e.g. the Nightly screencast in comment 1), but it's still noticeable.

But it lasts **many seconds** in a local enable-debug/disable-optimize build -- here's a screencast showing that, where we've got the broken rendering from t=0:27 to t=0:37 (ten full seconds).

I'm guessing (but haven't yet confirmed) that the limiting factor here (on when we switch from bad to good rendering) is whether we've gotten the new-tab-tile data back from Firefox's server that provides that.  If that is indeed true, then I would imagine that folks on slow connections might see this broken rendering for many seconds even in optimized official builds (looking something like this screencast).