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 part that we have just downloaded from 0. So even if we don't cache those parts we still report those as buffered. This attribute is more used as a hint to user where seek is possible. But since we have implemented range request, anywhere can be played if server has range request support. Note that if the server doesn't support range request, seek is not possible. So this behavior does not give a false idea about what can be played, just a little slower loading the evicted parts. -- 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 -~----------~----~----~----~------~----~------~--~---
