- From: Chris Double <chris.double@double.co.nz>
- Date: Fri, 28 Jan 2011 12:38:26 +1300
On Fri, Jan 28, 2011 at 12:22 PM, Steve Lacey <sjl at chromium.org> wrote: > > But for the media element I'd like to propose raw bytes instead of a > rate as this allows the developer to construct their own rates (if > needed) based on whatever window they want. It would also be useful to > separate audio from video. A suggestion might be: Raw bytes sounds good. > unsigned long audioBytesDecoded; > unsigned long videoBytesDecoded; > > Though this seems a little strange to have these specifically on the > media element as they reference particular media types. Another idea > would be to move these to the video element and also add > audioBytesDecoded to the audio element. Moving them to the video and audio element would mean you can't get the audioBytesDecoded on a video element which is what I'm assuming you want by having the two values. Note that the Mozilla implementation I proposed has had a counter proposal by another mozilla developer and is being developed further. See: https://bugzilla.mozilla.org/show_bug.cgi?id=580531 Chris. -- http://www.bluishcoder.co.nz
Received on Thursday, 27 January 2011 15:38:26 UTC