-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New HAR page doesn't appear to be created upon navigation #19
Comments
Hi @gitgrimbo can you try and see what you get from Browsertime against your test page, then we can see if it is a puppeteer issue as in #15 (comment) or an issue with the Chrome-har. Thanks |
I've not used Browsertime before, but I'll take a look when I can. In the meantime, here are some console statements from making the following changes to index.js#L194..L200 switch (message.method) {
case 'Page.frameStartedLoading':
case 'Page.frameScheduledNavigation':
{
// LOG
console.log(message.method);
const frameId = params.frameId;
const rootFrame = rootFrameMappings.get(frameId) || frameId;
// LOG
pages.forEach((page, pageIdx) => console.log(pageIdx, "page.__frameId", page.__frameId, "rootFrame", rootFrame));
It looks like there are four |
This is the test code. It loads
http://localhost:8080/
and then clicks on the only link on the page. Theindex.html
page has oneIMG
tag, oneIFRAME
tag and oneA
tag.index.html
iframe.html
index2.html
iframe2.html
One_black_Pixel.png
Copied from here, https://en.wikipedia.org/wiki/File:One_black_Pixel.png.
HARs
The
chrome-har
captured HAR shows all the requests collected as a single page. But there should be two pages, one forindex.html
and one forindex2.html
.The HAR captured from Chrome devtools after performing the test manually, correctly shows two pages (albeit in the wrong order here).
The text was updated successfully, but these errors were encountered: