Issue metadata
Sign in to add a comment
|
RDP Network Throttle Only Works Once Dev Tools Is Opened (To Any Dev Tool Tab)
Reported by
mbu...@gmail.com,
May 7 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Steps to reproduce the problem: 1. Use remote debugging protocol to: (1) open chrome, (2) attach to the open tab, (3) Enable network throttling. 2. In this throttled window, manually go to a website. The network throttling from step 1 WILL NOT be applied (bug). 3. Manually open the dev tool panel (any dev tool tab is fine, not just the network tab) in this window, and go to a website. The network throttling from step 1 WILL be applied (bug). What is the expected behavior? The remote debugging protocol enabled network throttling should be applied to page loads even if the dev tools are closed. What went wrong? The RDP network throttling is only applied once the dev tools are opened. This defeats the purpose of using the RDP to automate the browser for automation performance tests. Did this work before? Yes It used to work, but I'm unsure in which version. It seems to still be broken in canary. Does this work in other browsers? Yes Chrome version: 66.0.3359.139 Channel: stable OS Version: OS X 10.13.4 Flash Version: Shockwave Flash 29.0 r0
,
May 8 2018
As per comments #0 Tested this issue on reported chrome version 66.0.3359.139 using mac 10.13.1. Attaching screencast for reference. Steps: -------- 1.Following https://chromedevtools.github.io/devtools-protocol/ launched chrome from the terminal appending --remote-debugging-port=9222. 2.Launched separate chrome instance> chrome$ /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=2"" 3. Changed the network throttling to Slow 3g in the chrome instance of C#1 and navigated to news.google.com and observed throllting remained at Slow 3g and page opened accordingly. 4. Repeated the same as in steps #3 in chrome instance of C#2 and didnt observe much of difference navigating to news.google.com with/without dev tool opened. @Reporter: Could you please review the attached screen-cast and confirm if anything being missed here. If possible, please share a screencast/test file which helps us in triaging the issue in a better way. Thanks..!
,
May 10 2018
,
May 10 2018
I figured out the issue. In the past Network.emulateNetworkConditions() didn't require a previous call to Network.enable(). Now it does. As long as this new behavior is not a bug, then this issue can be dropped.
,
May 10 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 10 2018
,
May 10 2018
closing as per #4 -- we currently only apply network emulation when the network agent is enabled. For the record, the behavior changed here: https://chromium-review.googlesource.com/c/chromium/src/+/840423 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, May 8 2018