lighthouse: Some cross-frame requests never receive Network.loadingFinished events
Provide 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
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 1
- Comments: 16
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.
Thanks @niieani! We wouldn’t want to land that change directly, but we likely will develop a workaround for iframe document requests to mark as finished when we receive the response 👍
If you’re interested in exploring a PR for that, happy to accept 😃