[Bug 27790] [MSE] Some of the attributes returning TimeRanges objects seem to return a new object each time the getter is invoked

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27790

--- Comment #10 from Aaron Colwell <acolwell@google.com> ---
Boris,

Would just changing the spec to return the same object if the ranges haven't
changed, as Philip suggest, be sufficient? 

I'm worried about making this attribute a live object for the following
reasons:
1. It would become inconsistent with HTMLMediaElement.buffered behavior. I know
you don't like this, but I think there is something to be said for keeping all
TimeRanges attributes in the web platform behaving the same way especially if
they are highly related like the .buffered attributes are.

2. This is one of the oldest parts of the MSE spec and is likely to break sites
including large deployments like YouTube and Netflix for seemingly only
aesthetic gain.

3. There is no simple way for the web app to make its own copy. The TimeRanges
object doesn't have a way to clone itself so all web applications that wanted
to keep a copy have to implement their own cloning logic.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 13 January 2015 16:35:22 UTC