summaryrefslogtreecommitdiffstats
path: root/base/callback.h
diff options
context:
space:
mode:
authorevan@chromium.org <evan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-04-15 18:22:57 +0000
committerevan@chromium.org <evan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-04-15 18:22:57 +0000
commit26cfaf5d657b92f5f94eccc0a0b51c28caccbc5a (patch)
tree3f1c70fa80bce061afa2e655e32e7995f6a8517d /base/callback.h
parent5a6a7718ca4abee6709bf91cfbca76dc26eaecc3 (diff)
downloadchromium_src-26cfaf5d657b92f5f94eccc0a0b51c28caccbc5a.zip
chromium_src-26cfaf5d657b92f5f94eccc0a0b51c28caccbc5a.tar.gz
chromium_src-26cfaf5d657b92f5f94eccc0a0b51c28caccbc5a.tar.bz2
Rejigger how we format the display of bytes.
(Note that this does *not* touch the mega/mebi issue, despite my recent discussion of it.) What had been bugging me was that when downloading a file, you'd see it count up 10.7, 10.8, 10.9, *11*, 11.1. That is, previously when we rounded to displaying a trailing zero, we'd clip it off, which would make a download display like "11.1 / 50.2MB" jiggle to the left every time the trailing digit lined up. Now we try to always display three digits, which means we count up like 98.8, 98.9, *99.0*, 99.1, ... 99.9, 100, ... 101. This code is after fiddling the test into the shape I wanted it to be, then making the code produce that behavior. TEST=covered by unit test, updated with new expected behavior Review URL: http://codereview.chromium.org/1558025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@44671 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/callback.h')
0 files changed, 0 insertions, 0 deletions