UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3515.0 Safari/537.36

Steps to reproduce the problem:
Chrome version used by puppeteer:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/70.0.3508.0 Safari/537.36

1. Run the attached node script with the line 'await setIntercept(page);' commented out
2. Check the trace.json file for any images downloaded and note the time taken to download (or use this to see the network timeline https://chromedevtools.github.io/timeline-viewer/)
3. Run the attached node script with the line 'await setIntercept(page);' not commented out
4. Check the trace.json file for the same image in step 2 (or use this https://chromedevtools.github.io/timeline-viewer/ to see the timeline) and notice that it has downloaded faster than step 2 (or see in general the site has loaded faster on the network timeline)

What is the expected behavior?
The trace files from step 2 and step 4 would have the same network timeline given the emulation settings.

More broadly, Network.continueInterceptedRequest would still use the same throttling settings used by Network.emulateNetworkConditions 

What went wrong?
The trace files show different network timelines, with the webpage in step 4 loading faster than step 2

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 70.0.3515.0  Channel: n/a
OS Version: OS X 10.13.6
Flash Version: 

You can change the site used on this line 'const url = 'https://www.att.com/';'
 

Deleted: bug.js 1.3 KB

bug.js 1.3 KB View Download