Use page other than chrome://terms for bf-cache gatherer

[connorjclark]

lighthouse/core/gather/gatherers/bf-cache-failures.js

Lines 107 to 109 in 1d2a380

	// In theory, we should be able to use about:blank here
	// but that sometimes produces BrowsingInstanceNotSwapped failures.
	// DevTools uses chrome://terms as it's temporary page so we should stick with that.

Marking for 11.0 not because it is a breaking change, but to keep on our radar to check on "sometime in the future".

[connorjclark]

CDT still uses the terms page: https://source.chromium.org/chromium/chromium/src/+/main:third_party/devtools-frontend/src/front_end/panels/application/components/BackForwardCacheView.ts;l=249;drc=091da104d0b774fc03a50d63954565986b197369

[adamraine]

Using about:blank as the temp page still adds an extra "Internal error" when testing bfcache. I'll ping bfcache folks about this again.

@tunetheweb chrome://blank isn't a valid page unfortunately. Do you know any other chrome://xyz pages that might be less confusing to users but still avoid the bugs we see with about:blank.

[tunetheweb]

Yeah I was suggesting getting the Chrome team to add that page. Not sure of any that would be less confusing to be honest.

[tunetheweb]

chrome://print/ maybe?

[ghnp5]

Coming from #15223,
I was now trying to search about why do I see that page on every test! Now I understand :)
It's indeed confusing to us.

[pladaria]

Is this affecting the LCP metric? My page loads in ~1s but the LCP reports ~10s

[tunetheweb]

No, LCP is measured as a separate audit before this one.