Edward, any suggestion on what kind of UI makes sense?

+helenepark for motion expertise.

I'm not entirely sure at the moment. If you draw attention to the tab(s), a user may more likely switch to it, which then triggers the load. 

Is the current behaviour to keep showing the spinner and hostname? Can we do something different like fetch the HTML content and parse the title / grab favicon only, suspending the page rendering process. If tabs loading at the point Chrome decides there is memory pressure and needs to stop loading? In which case can we get the title / favicon. 

Does Chrome start unloading older unused tabs? Prioritising loading the new tabs.

We have plan to show favicon and host name. So think that should be fine.

I need to clarify a little. There are 2 situations:
1. When no memory pressure, background tab's loading is *delayed*. But they will load automatically after a while.
2. When under memory pressure, background tab's loading is *stopped*. They will not load automatically unless user selects it.

So for the 2nd situation, should we tell the user or not? You can assume the tab strip shows favicon and hostname. (currently showing spinner, but that will be fixed)

I'm inclined for now to not show any special indicator besides the favicon and hostname. 

Looking Firefox session restore model, where no background tabs are loaded except when made active, I didn't find the experience particularly grating. 

The important thing is a user being able to identify a tab so they can easily switch. For new sites where we don't have the favicon, I presume we show the default page icon?

One request I do want to make (probably a separate issue) is to only show the hostname and remove the protocol. Important in the truncated tab state where you'll  potentially just see a row of http:// / https://. In the future world where www. and m. would be hidden, it would make sense to reflect that in the title too.

I see. We can roll out the favicon and hostname version first.

And to answer the 2 questions:
1. Yes, default page icon will be used when we don't have favicon.
2. Yes, the protocol will be removed. I am even thinking about removing "www", if that makes sense to you.

> 2. Yes, the protocol will be removed. I am even thinking about removing "www", if that makes sense to you.

SGTM

Memory pressure signal currently is not reliable.

Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.