Wrong base URL in Chrome 66 about chrome-har HOT 7 CLOSED

No I think Puppeteer somehow changes the trace log? This project was built for https://github.com/sitespeedio/browsertime to that uses webdriver to get the trace log from Chrome. Best is to ask in the puppeteer project.

from chrome-har.

If I build in master with Chrome 66 beta it looks like this:

so I'm pretty sure something changed in Chrome 66. Let me collect a trace log and see if I can find out what.

from chrome-har.

Log example, will check more tonight: https://gist.github.com/soulgalore/2a48ff346a0dfdac101cb4fa99a3bfbc

from chrome-har.

Fixed in 0.3.1

from chrome-har.

It does not seem fixed in latest puppeteer version/chrome(1.8.0)

from chrome-har.

@vlad4800 please create an upstream bug then in puppeteer :) We use Chrome standalone for our testing with Browsertime and there it works. It seems like there are things that puppeteer do that change the trace log so it isn't the same as if you run with Chrome standalone (people have reported issues where the trace events are in the wrong order etc).

Best
Peter

from chrome-har.

Yeah, that's exactly the issue here if I look at the raw events, then order of: Network.requestWillBeSent, Network.responseReceived and Page.frameStartedLoading is not always the same.

So you mean installing a different Chrome version than the one that comes as default with Puppeteer?

from chrome-har.