[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 #5 from Boris Zbarsky <bzbarsky@mit.edu> ---
> my take is that returning a new object every time isn't terrible enough 

It's pretty terrible.  It's a behavior that only C++ implementors seem to think
is OK for a JS property get....  Not least because it's simple for them to do.

> Ensuring that .buffered returns the same object as long as it hasn't changed
> since last access

Can it change without the event loop spinning or script in some way invoking
browser APIs?  Because if not, then this is clearly the correct solution, imo.

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

Received on Friday, 9 January 2015 14:13:11 UTC