Adam Raine

Update: pausing workers doesn't work the same way as pausing frames:  Links: https://gist.github.com/adamraine/3cc8ac108ff1667cad8d10c994cd317b https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/common/features.cc;drc=97f94c6631e327c2c1a9891774b44fbba9e8e3bf;l=201

There are actually 2 upstream issues blocking this I guess: https://bugs.chromium.org/p/chromium/issues/detail?id=1352175

Testing https://keegandonley.com/blog/my-approach-to-connected-fitness, I consistently get the `NO_LCP` failure on Canary 98.0.4752.0 in DevTools. https://website-2-0-mr96oixpd-kdonley.vercel.app/blog/my-approach-to-connected-fitness works fine for me so the `NO_LCP` part looks like https://github.com/GoogleChrome/lighthouse/issues/10869. I'm also reproducing the `NO_FCP`...

This is a trace from a successful run on the CLI: https://gist.github.com/adamraine/91cbf9dc0c6d391e4264129d457cd2d7 It's showing FCP and LCP as the same element (big image at the top): ![Screen Shot 2021-12-07 at...

On my machine, the FCP error seems dependent on the viewport size. Taking just performance traces over a page load, the FCP starts to disappear for viewports wider than ~1375px....

FCP is missing in DevTools performance trace as well, so I filed a Chrome bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1278858

@mwt I'm getting NO_LCP not NO_FCP so that looks more like #10869

Split out https://github.com/GoogleChrome/lighthouse/pull/14217

I'm leaving this open, but I would like to get something working for FR before we start enabling worker events https://github.com/GoogleChrome/lighthouse/issues/14211

> any of the URLs We would need a `visitedUrls` list or something. > Any downsides there? During a timespan, if the usr goes from originA to originB, and originB...