Issue metadata
Sign in to add a comment
|
NetworkInspectorAgent is aware of navigations only at commit time with PlzNavigate. |
||||||||||||||||||||||||
Issue descriptionI took a look at the InspectorNetworkAgent class. InspectorNetworkAgent::WillSendRequest() should be called before the request is sent and on each redirect. But with PlzNavigate(--enable-browser-side-navigation), it is called after the navigation has been made. Indeed InspectorNetworkAgent::WillSendRequest() is called in the Renderer (in FrameFetchContext). It is a problem. For instance in Devtools > Network, requests for an iframe are not displayed until the responses are received. If you navigate to: <html> <img src="http://localhost:8080/navigation/resources/slow-resource.pl?delay=3000"></img> <iframe src="http://localhost:8080/navigation/resources/slow-resource.pl?delay=6000"></iframe> </html> You will see the pending request for the image, but not for the iframe. (See video) What do you think should be done for fixing the issue? We probably have to communicate these information from the browser process.
,
Sep 4 2017
Yes, I think it is.
,
Sep 4 2017
,
Sep 7 2017
,
Sep 8 2017
This is indeed a problem (although not the most important one), and I am not aware of easy ways to fix it. Let's keep this one in mind while cleaning up after PlzNavigate launch.
,
Sep 22 2017
,
Sep 22 2017
,
Sep 28 2017
DevTools team, do you plan on fixing this anytime soon? It seems that it affects a multitude of scenarios and PlzNavigate is now the default, so it will be good to have it fixed sooner rather than later.
,
Oct 2 2017
To fix this, we should instrument navigation request on the browser side and unify the request id between browser and renderer.
,
Oct 23 2017
Issue 767189 has been merged into this issue.
,
Oct 23 2017
See issue 767189 for download scenario, which has the same root cause.
,
Apr 11 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by alex...@chromium.org
, Sep 1 2017