Issue metadata
Sign in to add a comment
|
[Feature Request] per-file, per-domain and per-filetype throttling
Reported by
mkhatib...@gmail.com,
Mar 25 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2687.0 Safari/537.36 Steps to reproduce the problem: It'd be pretty awesome if one can throttle network but limit throttling to be for a specific file, domain or filetype. Usecases: * Throttling image requests to see how the website would look like if images served were slow-loading * Throttling API domain to see the effect of slow requests What is the expected behavior? What went wrong? Just couldn't throttle a specific file. Did this work before? N/A Chrome version: 51.0.2687.0 Channel: dev OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 21.0 r0
,
Mar 29 2016
,
Mar 30 2016
Origin seems reasonable, but the others don't seem realistic.
,
Mar 30 2016
To give some more context, I find myself sometimes wanting to slow down images (or a specific image) loading but not anything else. I can probably work around this with origin. One example is that I wanted to test the effect of having a thumbnail be slower to load than the video and what "race condition" could happen in case the thumbnail was pretty slow.
,
Apr 22 2016
,
Apr 23 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kozyatinskiy@chromium.org
, Mar 29 2016Status: Assigned (was: Unconfirmed)