Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gather-runner: can we reduce to just one pass? #11822

Closed
paulirish opened this issue Dec 14, 2020 · 6 comments
Closed

gather-runner: can we reduce to just one pass? #11822

paulirish opened this issue Dec 14, 2020 · 6 comments
Labels

Comments

@paulirish
Copy link
Member

Over in #11806 I'm removing the need for our offlinePass. And we've also removed the w/o javascript gatherer.

So in #11806 (comment) @brendankenny proposed we drop down to just 1 pass:

should service-worker move to redirectPass and only have two passes? service-worker would fail if the site doesn't redirect, but should http-redirect move to use driver.fetcher anyways?

and actually, with the new DevTools offline check, which is doing a real request, that means the ServiceWorker has to be activated and controlling the page. Presumably that means getServiceWorkerVersions/getServiceWorkerRegistrations will return the info, so do we even need a second pass anymore?

We'd move the 'service-worker' and 'http-redirect' gatherers to defaultPass and then we're good.


Patrick asked "can you request an insecure iframe on a secure page? I assume that would be blocked by mixed content" and noted: "no reason the offline pass needs to exist though"

@paulirish
Copy link
Member Author

Adam proposed that service-worker audit is removed as the instability errors surfaced in installable-manifest audit cover all the data we provide. Connor, Adam and I looked and it appears we might lose out on being definitive that the starturl isn't within SW scope. But there should still be an error. So we think its fine, given that it's not really LH's role to help you debug all SW things.

@connorjclark
Copy link
Collaborator

connorjclark commented Jan 24, 2022

We think we can remove service-worker audit and gatherer because installable-manifest seems to cover all the same cases well enough. With that, we could then be down to a single pass.

Removing that audit would require waiting for 10.0, but we could still remove the pass sooner if we changed the service-worker implementation to use InstallableManifest and try to recreate the audit result.

#11329 added some data which we might have trouble accurately recreating, and may mean we can't outright remove the service-worker audit. Brendan explained some of the complications of that in #9683 (comment)

@connorjclark
Copy link
Collaborator

With #13711 turns out we don't need to delete the audit at all, so this is def. not a breaking change.

@connorjclark
Copy link
Collaborator

With #13881 merged, can we close this?

@adamraine
Copy link
Member

Passes still exist but only in legacy navigation mode, so this is probably shuffling deck chairs on the titanic at this point.

@connorjclark
Copy link
Collaborator

Days are numbered for legacy, so let's not waste time on this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants