Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
start_url fetched via an "offline" SW not considered good enough
See original GitHub issueProvide the steps to reproduce
- Run LH on https://ondras.github.io/sw/
What is the current behavior?
start_url does not respond with a 200 when offline. The start_url did respond, but not via a service worker.
What is the expected behavior?
This configuration shall be considered okay.
The problem is related to the SW’s caching strategy. The current worker works online-first, i.e. it always tries to fetch the resource. It looks like it succeeds, even when “simulating offline in Lighthouse”, so the reply is not considered via a service worker.
If I change the if (cached) implementation to simply return cached (not trying any network interatction), Lighthouse works correctly.
Environment Information
- Affected Channels: DevTools
- Lighthouse version: 5.5, 5.7
- Chrome version: 79, 81
- Operating System: Linux
Issue Analytics
- State:
- Created 4 years ago
- Reactions:24
- Comments:17 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Fantastic news! Any idea when this will be integrated in to Chrome?
fixed in #11745