Some cross-frame requests never receive Network.loadingFinished events
See original GitHub issueProvide the steps to reproduce
- Run LH on https://www.oyorooms.com/us/
What is the current behavior?
No Network.loadingFinished
event for https://facebook.com/tr Document request will be in the devtools log.
What is the expected behavior?
https://facebook.com/tr has a Network.loadingFinished event.
Discovered while investigating https://github.com/GoogleChrome/lighthouse/issues/11849. The implications for this are that with enough of these requests (3 or more) Lighthouse will timeout while waiting for the page to load.
Environment Information
- Affected Channels: all
- Lighthouse version: all
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:16
Top Results From Across the Web
DevTools: Network.loadingFinished is never dispatched for ...
loadingFinished event is never dispatched for fetch requests that don't request their ... we cannot assume any URLRequest got to the end.
Read more >Network domain - Chrome DevTools Protocol - GitHub Pages
Network domain allows tracking network activities of the page. It exposes information about http, file, data and other requests and responses, their headers ......
Read more >selenium webdriver - Does `Network.loadingFinished` event ...
I am trying to using Selenium to analyse the performance of certain pages. I have a question about the Network events. When a...
Read more >The power of Chrome Devtools Protocol - Network domain
We will be recording some requests based on a Google search. ... which will be used to convert network events into a readable...
Read more >Remote Debugging - issues with Network.getResponseBody
loadedEventFired. If I modify my code to request the body of each resource immediately after I receive the Network.loadingFinished for that resource, a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
All throttling disabled is the same case as applied throttling, Lighthouse operating in “observed” metrics mode, so that would fall into the 5.25s of quiet.
Oh sorry for the miscommunication, by “that” I meant the “workaround for iframe document requests to mark as finished when we receive the response”. We don’t want to optionally exclude network idle requests just yet due to the standard definition we follow for TTI and TBT which do not have this concept in other tooling.