-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Comments
Adam proposed that |
We think we can remove Removing that audit would require waiting for 10.0, but we could still remove the pass sooner if we changed the #11329 added some data which we might have trouble accurately recreating, and may mean we can't outright remove the |
With #13711 turns out we don't need to delete the audit at all, so this is def. not a breaking change. |
With #13881 merged, can we close this? |
Passes still exist but only in legacy navigation mode, so this is probably shuffling deck chairs on the titanic at this point. |
Days are numbered for legacy, so let's not waste time on this! |
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:
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"
The text was updated successfully, but these errors were encountered: