- From: <bugzilla@jessica.w3.org>
- Date: Thu, 18 Apr 2013 22:56:36 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20760 --- Comment #7 from Aaron Colwell <acolwell@google.com> --- (In reply to comment #6) > (In reply to comment #5) > > I too would like to see something a little simpler. How about this? > > > > partial interface HTMLMediaElement { > > attribute readonly MediaPlaybackQuality playbackQuality > > } > > We made this a method because we don't think the return object should be > live. It's tough to use the values if they change while you're using them. I agree with that idea. That is why I suggested that a new object be created on each read. The idea is to make it like the buffered attribute that indicates that a new static object is created on each read. > > > interface MediaPlaybackQuality { > > readonly attribute unsigned long totalVideoFrames; > > readonly attribute unsigned long droppedVideoFrames; > > }; > > Since we didn't want the return value to be live, we added a timestamp so > that you could use that to compare against a previous time. I figured the application could just fetch whatever timestamp it needed right before reading the attribute. This could be a Date or say a requestAnimationFrame() timestamp or something else. I don't think the latency between the two calls would be significant enough to throw off accuracy in any major way. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 18 April 2013 22:56:37 UTC