On Fri, 10 Dec 2010 01:43:27 +0100, Kevin Carle kca...@google.com wrote:
The use case under discussion is changing to another video. So the
element
is already inserted and already has src.
Something like:
video controls autoplay
source src=video1.webm type=video/webm
source src=video1.mp4
On Thu, Dec 9, 2010 at 1:42 AM, Simon Pieters sim...@opera.com wrote:
On Thu, 09 Dec 2010 02:58:12 +0100, Ian Hickson i...@hixie.ch wrote:
On Wed, 1 Sep 2010, Simon Pieters wrote:
I think it might be good to run the media element load algorithm when
setting or changing src on source (that
On Wed, 1 Sep 2010, Simon Pieters wrote:
I think it might be good to run the media element load algorithm when
setting or changing src on source (that has a media element as its
parent), but not type and media (what's the use case for type and
media?). However it would fire an 'emptied'
On Wed, 28 Jul 2010 10:59:13 +0200, Philip Jägenstedt phil...@opera.com
wrote:
I'm just saying that it shouldn't work if implementations follow the
spec. I don't think that it *not* working is a feature, but I also don't
think that making it work is very important. In the example the
On Wed, 28 Jul 2010 01:10:07 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Tue, Jul 27, 2010 at 6:17 PM, Philip Jägenstedt
phil...@opera.comwrote:
On Tue, 27 Jul 2010 00:01:26 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Tue, Jul 27, 2010 at 1:37 AM, Philip
On Tue, Jul 27, 2010 at 6:17 PM, Philip Jägenstedt phil...@opera.comwrote:
On Tue, 27 Jul 2010 00:01:26 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Tue, Jul 27, 2010 at 1:37 AM, Philip Jägenstedt phil...@opera.com
wrote:
On Mon, 26 Jul 2010 16:53:43 +0200, Silvia Pfeiffer
I actually don't think there's anything wrong about the spec as it is.
NETWORK_NO_SOURCE is not a state of failure, it is a waiting state. Here's
what happens as the parser inserts elements into the DOM:
video controls width=400px
!-- video has been inserted but resource selection hasn't run
On Mon, 26 Jul 2010 02:58:07 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Sun, Jul 25, 2010 at 3:31 PM, Maciej Stachowiak m...@apple.com wrote:
On Jul 23, 2010, at 7:16 AM, Philip Jägenstedt wrote:
Silvia made we aware of discrepancy in how browsers implement the
resource
On Mon, Jul 26, 2010 at 7:41 PM, Philip Jägenstedt phil...@opera.comwrote:
I actually don't think there's anything wrong about the spec as it is.
NETWORK_NO_SOURCE is not a state of failure, it is a waiting state. Here's
what happens as the parser inserts elements into the DOM:
video
On Mon, 26 Jul 2010 14:53:50 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Mon, Jul 26, 2010 at 7:41 PM, Philip Jägenstedt
phil...@opera.comwrote:
I actually don't think there's anything wrong about the spec as it is.
NETWORK_NO_SOURCE is not a state of failure, it is a
On Mon, Jul 26, 2010 at 11:12 PM, Philip Jägenstedt phil...@opera.comwrote:
On Mon, 26 Jul 2010 14:53:50 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Mon, Jul 26, 2010 at 7:41 PM, Philip Jägenstedt phil...@opera.com
wrote:
I actually don't think there's anything wrong
On Mon, 26 Jul 2010 15:02:34 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Mon, Jul 26, 2010 at 7:49 PM, Philip Jägenstedt
phil...@opera.comwrote:
On Mon, 26 Jul 2010 02:58:07 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Sun, Jul 25, 2010 at 3:31 PM, Maciej
On Mon, Jul 26, 2010 at 11:25 PM, Philip Jägenstedt phil...@opera.comwrote:
On Mon, 26 Jul 2010 15:02:34 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Mon, Jul 26, 2010 at 7:49 PM, Philip Jägenstedt phil...@opera.com
wrote:
On Mon, 26 Jul 2010 02:58:07 +0200, Silvia
On Mon, 26 Jul 2010 16:53:43 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Mon, Jul 26, 2010 at 11:25 PM, Philip Jägenstedt
phil...@opera.comwrote:
On Mon, 26 Jul 2010 15:02:34 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Mon, Jul 26, 2010 at 7:49 PM, Philip
On Sun, Jul 25, 2010 at 3:31 PM, Maciej Stachowiak m...@apple.com wrote:
On Jul 23, 2010, at 7:16 AM, Philip Jägenstedt wrote:
Silvia made we aware of discrepancy in how browsers implement the resource
selection algorithm, see forwarded message. It's my assessment that Opera is
the only
On Jul 23, 2010, at 7:16 AM, Philip Jägenstedt wrote:
Silvia made we aware of discrepancy in how browsers implement the resource
selection algorithm, see forwarded message. It's my assessment that Opera is
the only browser following the spec. I've filed this bug with Mozilla:
Silvia made we aware of discrepancy in how browsers implement the resource
selection algorithm, see forwarded message. It's my assessment that Opera
is the only browser following the spec. I've filed this bug with Mozilla:
https://bugzilla.mozilla.org/show_bug.cgi?id=581355
I've also
On 24/07/2010 2:16 a.m., Philip Jägenstedt wrote:
Silvia made we aware of discrepancy in how browsers implement the
resource selection algorithm, see forwarded message. It's my
assessment that Opera is the only browser following the spec. I've
filed this bug with Mozilla:
There is definitely a spec bug, because different locations of the spec say
diverging things. While the first step in the resource selection algorithm
states to go into NETWORK_NO_SOURCE state, the description of
NETWORK_NO_SOURCE in the spec actually implies a state of failure. Since the
first
19 matches
Mail list logo
