Comment #15 on issue 16056 by [email protected]: [HTML5-Video] layout
test on buffered attribute fails in Chrome
http://code.google.com/p/chromium/issues/detail?id=16056
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=22822
------------------------------------------------------------------------
r22822 | [email protected] | 2009-08-07 16:08:23 -0700 (Fri, 07 Aug
2009) | 26 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/branches/195/src/media/base/mock_filters.h?r1=22822&r2=22821
M
http://src.chromium.org/viewvc/chrome/branches/195/src/media/base/pipeline_impl.cc?r1=22822&r2=22821
M
http://src.chromium.org/viewvc/chrome/branches/195/src/media/base/pipeline_impl_unittest.cc?r1=22822&r2=22821
Merge 22087 - Missing buffered attribute for <video>/<audio>
BUG=16056
TEST=LayoutTests/media/videobuffered.html
The current implementation of the buffered attribute for <video> and <audio>
is broken. There are several problems around this attribute:
1. We don't have any caching on disk, so we only keep a recent range of
bytes
close to current playback position.
2. WebKit reports buffered as one range (0, max_time_buffered). But we only
cache a short partial range which doesn't start with 0. The correct
implementation is a list of ranges buffered. But this has to go into
WebKit
first.
3. We don't have an accurate mapping between byte offset < > timestamp.
So the current implementation is to lie about what we have buffered. We
always
say we have buffered everything before the current download position. And we
only report one range. The calculation of time is also based on scaling the
duration with current buffered bytes.
Review URL: http://codereview.chromium.org/160300
[email protected]
Review URL: http://codereview.chromium.org/165180
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
