1411125 - New Tab Favicon appears with a delay

Status: RESOLVED DUPLICATE of bug 1401955

(Firefox :: New Tab Page, enhancement)

Description

[(Currently slow to respond) Philipp Sackl [:phlsa] (Firefox UX) please use needinfo]

Attachment: favicon appearing with delay

In 57, we added a favicon to the newtab page. The problem is that this favicon appears with a delay when opening a new tab, making the process of opening a tab look janky and less performant (see video in attachment for a demonstration)

I see two options here:
1. (highly preferred): Already show the favicon during the tab open animation
2. (if 1. isn't feasible): reserve the space for the favicon during the tab open animation, so that at least the text doesn't jump around.

Comment 1

[Marco Bonardo [:mak]]

The favicons are fetched on a timer now, plus they use tailing in network, so a delay is expected. We should reserve the space.

Comment 2

[Dão Gottwald [:dao]]

(In reply to (Currently slow to respond) Philipp Sackl [:phlsa] (Firefox UX) please use needinfo from comment #0)
> In 57, we added a favicon to the newtab page.

Why? :( This doesn't seem useful and hides the tab label as tabs shrink.

(In reply to Marco Bonardo [::mak] from comment #1)
> The favicons are fetched on a timer now, plus they use tailing in network,
> so a delay is expected.

about:newtab uses a local icon.

> We should reserve the space.

This sounds like a not so great solution for pages without favicons.

Comment 4

[Marco Bonardo [:mak]]

(In reply to Dão Gottwald [::dao] from comment #2)
> about:newtab uses a local icon.

It doesn't matter if it's set through a <link> meta tag, it still goes through the same code path as a remote icon.

Comment 5

[Dão Gottwald [:dao]]

(In reply to Marco Bonardo [::mak] from comment #4)
> (In reply to Dão Gottwald [::dao] from comment #2)
> > about:newtab uses a local icon.
> 
> It doesn't matter if it's set through a <link> meta tag, it still goes
> through the same code path as a remote icon.

Maybe so, but having favicons appear perceivably later because of that implementation detail doesn't sound right.