[Bug 12529] Fix HAVE_METADATA and HAVE_CURRENT_DATA when seeking and at playback end

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12529

Philip Jägenstedt <philipj@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |philipj@opera.com

--- Comment #1 from Philip Jägenstedt <philipj@opera.com> 2011-04-20 08:33:58 UTC ---
http://lists.w3.org/Archives/Public/public-html/2011Feb/0441.html
http://lists.w3.org/Archives/Public/public-html/2011Feb/0451.html

Based on this discussion, some spec changes are in order.

On Fri, 25 Feb 2011 22:45:16 +0100, Philip Jägenstedt <philipj@opera.com>
wrote:

> Suggestion:
>
> * buffered ranges are inclusive
> * whenever currentTime is not in one of the ranges, readyState <=  
> HAVE_METADATA
> * when currentTime is in one of the ranges, readyState >=  
> HAVE_CURRENT_DATA
> * no special casing of EOS
>
> This would mean that readyState would never go back to HAVE_METADATA  
> during normal playback, only when first loading the resource and when  
> seeking to an unbuffered position. At least to me, this seems consistent  
> and logical.

On Sat, 26 Feb 2011 14:46:50 +0100, Philip Jägenstedt <philipj@opera.com>
wrote:

> I'd much prefer if we kept the theoretical model and definitions simple  
> by not assuming that there's such a thing as an imaginary epsilon  
> differentiating two times that are indistinguishable both to the browser  
> internals and via the DOM API.

The definition of "potentially playing" might need readjusting as well, as it
was changed during that discussion.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 20 April 2011 08:34:01 UTC