Throttling does not extend to windows launched from the throttled page.
Reported by
davmil...@gmail.com,
Nov 20
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Steps to reproduce the problem: 1. Create a page that launches a new window, and set it up to wait for a particular global function to be present in the loaded page. 2. Open the parent page in a tab with throttling/offline turned on. 3. Run the code that launches the new window. What is the expected behavior? The new window is unable to load due to offline simulation, or loads slowly due to throttling. What went wrong? The new window did not have any throttling applied and was able to load without problems. Did this work before? N/A Chrome version: 70.0.3538.67 Channel: stable OS Version: Fedora 29 Flash Version:
,
Nov 21
,
Nov 21
Thanks for filing the issue.. @reporter: Could you please provide a sample file or URL that reproduces the issue, so that it would be really helpful for triaging it.
,
Nov 26
This is true. Throttling is only applied to the currently inspected tab. You can use the "auto-open devtools for popups" checkbox in settings to open devtools for new windows, though I'm not sure if the throttling will be applied automatically. |
||||
►
Sign in to add a comment |
||||
Comment 1 by davmil...@gmail.com
, Nov 20