Comment #15 on issue 16056 by bugdro...@chromium.org: [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
Comment #12 on issue 16056 by scher...@chromium.org: [HTML5-Video] layout
test on buffered attribute fails in Chrome
http://code.google.com/p/chromium/issues/detail?id=16056
For reference, Firefox handles it in a way that sounds pretty consistent
with what you
want to do (they're also updati
Comment #11 on issue 16056 by hc...@chromium.org: [HTML5-Video] layout test
on buffered attribute fails in Chrome
http://code.google.com/p/chromium/issues/detail?id=16056
I'm inclined to use a simple approach first, i.e. to lie about the buffered
range. We can
report the range up until the p
Comment #10 on issue 16056 by scher...@chromium.org: [HTML5-Video] layout
test on buffered attribute fails in Chrome
http://code.google.com/p/chromium/issues/detail?id=16056
Alpha's got it right.
What about the having the following behaviour:
1) Report [0,duration] for file:// sources (it'
