W3C home > Mailing lists > Public > public-html@w3.org > February 2011

(unknown charset) Re: <video> readyState oddities

From: (unknown charset) Ian Hickson <ian@hixie.ch>
Date: Fri, 18 Feb 2011 20:42:46 +0000 (UTC)
To: (unknown charset) Chris Pearce <chris@pearce.org.nz>
cc: (unknown charset) Philip J├Ągenstedt <philipj@opera.com>, HTML WG <public-html@w3.org>
Message-ID: <Pine.LNX.4.64.1102182025510.28618@ps20323.dreamhostps.com>
On Thu, 17 Feb 2011, Chris Pearce wrote:
> > 
> > 2. When you run out of buffered data when playing normally, should 
> > readyState revert to HAVE_CURRENT_DATA or HAVE_METADATA? The answer 
> > depends on what currentTime is at that point, it seems.
> Firefox won't drop below HAVE_CURRENT_DATA once it's passed it, the 
> logic being that we're still able to display the frame which we're 
> currently displaying. So we drop back to HAVE_CURRENT_DATA in this case.

The spec currently states that CURRENT_DATA is for when "Data for the 
immediate current playback position is available", so per spec this would 
be wrong.

I think it is relatively important to have the spec's behaviour; without 
it, it's impossible for the author to know if you're displaying what he 
wants you to display or if you're still trying to decode it.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 18 February 2011 20:43:15 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:09 UTC