Custom network throttle profiles assume kB(ytes)/s input instead of k(bits)/s
Reported by
l.duerre...@gmail.com,
Mar 27 2017
|
|
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Open the network tab 2. Select "Custom > Add..." in the throttle profile list 3. Add a new profile 4. Use a download/upload rate of 10000 5. Click "Save" and watch the value being turned into 9.8 Mb/s What is the expected behavior? The expected unit should be kb(it)/s, so 10000 kb/s = 10 Mb/s What went wrong? The code assumes the input as kB(ytes)/s and thus does a division by 1024 instead of 1000. Did this work before? N/A Chrome version: 56.0.2924.87 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: This is most likely an oversight when switching from Bytes to Bits display (as it should be) in https://bugs.chromium.org/p/chromium/issues/detail?id=532860
,
Apr 7 2017
So you're saying that because fixing one bug other bugs could appear, that you won't fix the bug? Do you treat all bugs like that? The changes required to fix this bug are pretty much the same as the changes done for the other bug I linked. How come that it wasn't "too much hassle" for the other bug, but this bug here can be ignore?
,
Apr 7 2017
Hey Blaise, can you double-check if I am missing something? The network panel uses “kb” as its unit. It is unclear to me whether that means kB (= 1000 B) or KB (=1024B). I think the OP is requesting to have that clarified on way or the other. |
|
►
Sign in to add a comment |
|
Comment 1 by allada@chromium.org
, Apr 6 2017