Ian Hickson wrote:
On Mon, 6 Oct 2008, Bonner, Matt wrote:
the original proposal said:
var playing = !video.paused
!video.ended video.readyState = HTMLMediaElement.CAN_PLAY
you appear to be proposing:
var playing = !video.paused video.readyState =
HTMLMediaElement.CAN_PLAY
media element details
If video.ended is true, what happens to video.readyState ? Because if the
video ends, I think most page authors would want buttons like pause to
be disabled. No?
Matt
--
Matt Bonner
Hewlett-Packard Company
Ok I totally lost this thread, sorry.
Ian Hickson wrote:
On Fri, 23 May 2008, Bonner, Matt (IPG) wrote:
Knowing if the playback is progressing is necessary for
implementing basic playback UIs with JS. It is clumsy and not
very obvious that you need to do var playing = !video.paused
] On Behalf Of Ian Hickson
Sent: Thursday, June 12, 2008 2:36 AM
To: Antti Koivisto
Cc: [EMAIL PROTECTED]
Subject: Re: [whatwg] Some media element details
The state of a play/pause button is definitely not correlated to the
playback state. It's correlated to the paused boolean.
On Fri, 16 May 2008, Antti Koivisto wrote:
[It would be nice to have a read-only attribute (called playing for
example) that would be true when the element is actively playing.
Knowing if the playback is progressing is necessary for implementing
basic playback UIs with JS. It is clumsy
On Fri, 16 May 2008, James Justin Harrell wrote:
The current HTMLMediaElement interface is inconsistent and is designed
in such a way that making changes to it will be extremely difficult.
The network state is given by the networkState attribute, and is one
of: EMPTY, LOADING,
On Fri, 23 May 2008, Bonner, Matt (IPG) wrote:
Knowing if the playback is progressing is necessary for
implementing basic playback UIs with JS. It is clumsy and not
very obvious that you need to do var playing = !video.paused
!video.ended video.readyState =
Hewlett-Packard Company
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian Hickson
Sent: Friday, May 16, 2008 3:20 PM
To: Bonner, Matt (IPG)
Cc: [EMAIL PROTECTED]; Antti Koivisto
Subject: Re: [whatwg] Some media element details
On Fri, 16 May 2008
On Mon, 14 Jan 2008, Ian Hickson wrote:
On Mon, 14 Jan 2008, Antti Koivisto wrote:
It would be nice to have a read-only attribute (called playing for
example) that would be true when the element is actively playing.
Knowing if the playback is progressing is necessary for implementing
On Fri, 16 May 2008, Bonner, Matt (IPG) wrote:
On Mon, 14 Jan 2008, Ian Hickson wrote:
On Mon, 14 Jan 2008, Antti Koivisto wrote:
It would be nice to have a read-only attribute (called playing for
example) that would be true when the element is actively playing.
Knowing if the
On 14.5.2008, at 23:37, Ian Hickson wrote:
It would be nice to have a read-only attribute (called playing for
example) that would be true when the element is actively playing.
Knowing if the playback is progressing is necessary for implementing
basic playback UIs with JS. It is clumsy and not
The current HTMLMediaElement interface is inconsistent and is designed in such
a way that making changes to it will be extremely difficult.
The network state is given by the networkState attribute, and is one of:
EMPTY, LOADING, LOADED_METADATA, LOADED_FIRST_FRAME, LOADED
The ready state is
On May 16, 2008, at 9:29 PM, James Justin Harrell wrote:
The current HTMLMediaElement interface is inconsistent and is
designed in such a way that making changes to it will be extremely
difficult.
The network state is given by the networkState attribute, and is
one of:
EMPTY, LOADING,
On Mon, 14 Jan 2008, Antti Koivisto wrote:
Some comments about the media elements:
3.14.9.4. Loading the media resource
The user agent must then set the begun flag to true and fire a progress
event called begin at the media element.
The progress event draft calls this event
14 matches
Mail list logo
