Issue 41603 in chromium: HTML5 Video "progress" event lacks information about buffered/total bytes

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: OS-Linux Area-Undefined Type-Bug

New issue 41603 by pcxunlimited: HTML5 Video "progress" event lacks
information about buffered/total bytes
http://code.google.com/p/chromium/issues/detail?id=41603

Chrome Version (from the about:version page): 5.0.375.3 (Official Build
44229) dev
Is this the most recent version: Yes
OS + version: Debian GNU/Linux 5.0.4 (Lenny)
CPU architecture (32-bit / 64-bit): 64-bit
Window manager: GNOME/Metacity
URLs (if relevant): N/A
Behavior in Linux Firefox: Haven't checked yet
Behavior in Windows Chrome (if you have access to it): Don't know

What steps will reproduce the problem?
1. Attach the "progress" event to any HTML5 <video>.
2. Try to find out how much has been loaded, the total duration of the
video, etc.

What is the expected result?
The properties would exist and have useful information.

What happens instead?
The properties are undefined.

Please provide any additional information below. Attach a screenshot
and backtrace if possible.
According to the MDC, there are various useful properties attached directly
to the <video> tag: buffered, bufferedBytes, and totalBytes. None contain
useful information.

In addition, on the "progress" event itself, there are supposed to be three
properties: lengthComputable, loaded, and total. These also do not contain
useful information.

I am building a custom UI for <video> elements. It works great, except that
I have no way to show the user what percentage of the video has loaded. I
need the information provided above in order to do this.

I don't need TimeRanges, I only need to know the total number of bytes in
the video, and how many bytes have been buffered.

Here are the relevant MDC pages:

https://developer.mozilla.org/En/NsIDOMHTMLMediaElement
https://developer.mozilla.org/En/Using_audio_and_video_in_Firefox

--
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

[chro...@googlecode.com]

Comment #4 on issue 41603 by pcxunlimited: HTML5 Video "progress" event

lacks information about buffered/total bytes
http://code.google.com/p/chromium/issues/detail?id=41603

Fair enough, though I would still like to see the buffered attribute
supported in the
future. Right now, it doesn't report any useful data.

The seekable property would also be very useful, but that would be best as
a separate
bug report, I think.

--
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/a/chromium.org/group/chromium-bugs

[chro...@googlecode.com]

Comment #5 on issue 41603 by johndyer: HTML5 Video "progress" event lacks

information about buffered/total bytes
http://code.google.com/p/chromium/issues/detail?id=41603

The buffered TimeRanges are very useful for showing the sections of the
media that have been loaded. However, Chrome currently always reports one
TimeRange with 100% loaded. So at present it is useless.

[chro...@googlecode.com]

Comment #7 on issue 41603 by yehia.sh...@gmail.com: HTML5 Video "progress"

event lacks information about buffered/total bytes
http://code.google.com/p/chromium/issues/detail?id=41603

In fact, and coming from a Flash world. Regardless of what method is used
for data download whether http streaming (allowing seek in unloaded area) -
or straight forward progressive download..

Reporting bytesLoaded and bytesTotal can give us lots of changes for
interactivity.

1. reflecting loaded amount/cached amount through a bar/seekbar
2. playing back video in a segmented manner in chapters (which is a use
case i faced in a project before) - I was able to play through 20% of the
video and then display some text, the user would click next to continue
playing the rest.
3. if i am building a video editor, i would need to know if my assets are
loaded.

Mozilla didn't follow HTML5 specs that much when they created their Audio
API. And Adobe used to give us tools and then see what the creative
community can do with it.

I see this as a serious limitation for all media elements.