You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was a suggestion that this may have been fixed, however we still don’t appear to correctly represent DNS failures in the waterfall chart.
There are two different cases of where the failure can occur, and each behaves slightly differently:
Where the root request fails (e.g. await page.goto("http://www.thisisaninvaliddomain.com")), this shows nothing in the waterfall chart
Where a non root network request results in a DNS failure, in which case we show a row/entry on the waterfall chart, but don’t show any DNS timing data for it (i.e. how long it took for the DNS lookup to take place, and fail)
The text was updated successfully, but these errors were encountered:
There was a suggestion that this may have been fixed, however we still don’t appear to correctly represent DNS failures in the waterfall chart.
There are two different cases of where the failure can occur, and each behaves slightly differently:
await page.goto("http://www.thisisaninvaliddomain.com")
), this shows nothing in the waterfall chartThe text was updated successfully, but these errors were encountered: