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.
Improve generalized/sourcemap fetcher
See original GitHub issuehttps://github.com/GoogleChrome/lighthouse/pull/9459 landed our generalized fetcher (with an iframe).
We may have some areas where it can be improved.
CSP sensitivity… I didn’t test, but I believe a frame-src directive would introduce problems for this technique.
content-type sensitivity. In #12064 we see that if a map is served with application/octet-stream it’ll trigger a user-visible download while Lighthouse is fetching it. DevTools, meanwhile, doesn’t have that behavior when it fetches.
devtools generalized loading…
There’s been some updates…
Sigurd added the Network.loadNetworkResource protocol method for sourcemaps. He recently added metrics to record how various load attempts succeed/fail.
AFAICT, there are currently four different types of fetch attempts… you can see them in PageResourceLoader.js’s _dispatchLoad() in the devtools source.
Here’s the umbrella crbug.
You can also see some of this in the new “Developer Resources” drawer panel in devtools:
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 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
We’re using the new protocol method to fetch resources now, but we need to keep the old one around for LR: #13006
Let’s track in #13394 – next month we should be able to drop the iframe fetcher completely.
https://proxx.app/ also reproduces this behavior.