On Tue, 28 Jul 2009 02:39:46 +0200, Andrew Scherkus scher...@google.com
wrote:
On Sun, 12 Jul 2009, Philip Jägenstedt wrote:
Not that I except this discussion to go anywhere, but out of
curiosity I
checked how Firefox/Safari/Chrome actually implement canPlayType:
On Fri, 10 Jul 2009, Aryeh Gregor wrote:
On Fri, Jul 10, 2009 at 4:57 AM, Robert O'Callahanrob...@ocallahan.org
wrote:
The way we've implemented in Firefox, we'll return yes if you
specify a codecs parameter and we support every codec in your list. So
v.canPlayType(video/ogg;
On Mon, Jul 27, 2009 at 3:48 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 10 Jul 2009, Aryeh Gregor wrote:
On Fri, Jul 10, 2009 at 4:57 AM, Robert O'Callahanrob...@ocallahan.org
wrote:
The way we've implemented in Firefox, we'll return yes if you
specify a codecs parameter and we
On Mon, 13 Jul 2009 00:00:20 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
On Sun, Jul 12, 2009 at 10:34 AM, Philip Jägenstedt
phil...@opera.comwrote:
Not that I except this discussion to go anywhere, but out of curiosity I
checked how Firefox/Safari/Chrome actually implement
On Mon, Jul 13, 2009 at 1:43 AM, Philip Jägenstedt phil...@opera.comwrote:
Also, I've reported bugs on Safari and Chrome (I think, neither give
confirmation that the report has been sent successfully!)
That's odd. Both bugs.webkit.org and crbug.com tell me when I've filed a
bug, and give me
On Sun, Jul 12, 2009 at 3:44 AM, Philip Jägenstedt phil...@opera.comwrote:
On Sat, 11 Jul 2009 14:38:02 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
On Sat, Jul 11, 2009 at 11:51 PM, Philip Jägenstedt phil...@opera.com
wrote:
Yes, I'm saying that when codecs are provided true
On Sun, Jul 12, 2009 at 10:34 AM, Philip Jägenstedt phil...@opera.comwrote:
Not that I except this discussion to go anywhere, but out of curiosity I
checked how Firefox/Safari/Chrome actually implement canPlayType:
http://wiki.whatwg.org/wiki/Video_type_parameters#Browser_Support
Firefox is
2009/7/13 Robert O'Callahan rob...@ocallahan.org:
On Mon, Jul 13, 2009 at 10:00 AM, Robert O'Callahan rob...@ocallahan.org
wrote:
It's not hard to implement this right, these issues reflect sloppy
development more than a fundamental problem IMHO.
That sounded mean, I apologize. What I want
On Mon, Jul 13, 2009 at 11:14 AM, David Gerard dger...@gmail.com wrote:
Should clarified wording be written up for the spec?
The wording's fine.
Rob
--
He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his
On Sat, 11 Jul 2009 03:35:22 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
On Sat, Jul 11, 2009 at 9:37 AM, Philip Jagenstedt
phil...@opera.comwrote:
the point is simply that calling canPlayType without out a codecs list
or
with specific codecs, you can learn exactly what is
On Sat, 11 Jul 2009 03:31:50 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
On Sat, Jul 11, 2009 at 5:23 AM, Aryeh Gregor
simetrical+...@gmail.comsimetrical%2b...@gmail.com
wrote:
Maybe you'd try testing all the video types you support, and
if one is maybe while another is probably
On Sat, Jul 11, 2009 at 9:38 PM, Philip Jägenstedt phil...@opera.comwrote:
Well I disagree of course, because having canPlayType(video/ogg) mean
anything else than can I demux Ogg streams is pointless.
So you want canPlayType to mean one thing when provided a type without
codecs, and another
On Sat, 11 Jul 2009 13:15:14 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
On Sat, Jul 11, 2009 at 9:38 PM, Philip Jägenstedt
phil...@opera.comwrote:
Well I disagree of course, because having canPlayType(video/ogg) mean
anything else than can I demux Ogg streams is pointless.
So
2009/7/11 Robert O'Callahan rob...@ocallahan.org
On Sat, Jul 11, 2009 at 9:38 PM, Philip Jägenstedt phil...@opera.comwrote:
Well I disagree of course, because having canPlayType(video/ogg) mean
anything else than can I demux Ogg streams is pointless.
So you want canPlayType to mean one
On Sat, 11 Jul 2009 14:38:02 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
On Sat, Jul 11, 2009 at 11:51 PM, Philip Jägenstedt
phil...@opera.comwrote:
Yes, I'm saying that when codecs are provided true means probably and
otherwise it means maybe, because the distinction is
On Jul 10, 2009, at 6:31 PM, Robert O'Callahan wrote:
On Sat, Jul 11, 2009 at 5:23 AM, Aryeh Gregor simetrical+...@gmail.com
wrote:
Maybe you'd try testing all the video types you support, and
if one is maybe while another is probably you'd go with
probably?
Right. Or you might have
On Jul 11, 2009, at 7:56 AM, Ian Fette (イアンフェッティ) wrote:
2009/7/11 Robert O'Callahan rob...@ocallahan.org
On Sat, Jul 11, 2009 at 9:38 PM, Philip Jägenstedt
phil...@opera.com wrote:
Well I disagree of course, because having canPlayType(video/ogg)
mean anything else than can I demux Ogg
On Sat, 11 Jul 2009 21:15:47 +0200, Maciej Stachowiak m...@apple.com
wrote:
On Jul 11, 2009, at 7:56 AM, Ian Fette (イアンフェッティ) wrote:
2009/7/11 Robert O'Callahan rob...@ocallahan.org
On Sat, Jul 11, 2009 at 9:38 PM, Philip Jägenstedt
phil...@opera.com wrote:
Well I disagree of course,
On Jul 11, 2009, at 3:34 PM, Philip Jägenstedt wrote:
Not that I except this discussion to go anywhere, but out of
curiosity I checked how Firefox/Safari/Chrome actually implement
canPlayType:
http://wiki.whatwg.org/wiki/Video_type_parameters#Browser_Support
Firefox is conservative and
Robert O'Callahan wrote:
On Fri, Jul 10, 2009 at 7:36 PM, James Graham jgra...@opera.com wrote:
Is there a good reason to return the empty string rather than false? The
empty string seems very unhelpful to authors since it doesn't play nicely
with debugging prompts and is non-obvious to infer
On Fri, Jul 10, 2009 at 4:57 AM, Robert O'Callahanrob...@ocallahan.org wrote:
The way we've implemented in Firefox, we'll return yes if you specify a
codecs parameter and we support every codec in your list. So
v.canPlayType(video/ogg; codecs=vorbis,theora) returns probably in
Firefox 3.5. I
On Fri, 10 Jul 2009 19:23:44 +0200, Aryeh Gregor
simetrical+...@gmail.com wrote:
On Fri, Jul 10, 2009 at 4:57 AM, Robert O'Callahanrob...@ocallahan.org
wrote:
The way we've implemented in Firefox, we'll return yes if you specify
a
codecs parameter and we support every codec in your list. So
On Fri, 10 Jul 2009 23:26:40 +0200, Philip Jagenstedt phil...@opera.com
wrote:
On Fri, 10 Jul 2009 19:23:44 +0200, Aryeh Gregor
simetrical+...@gmail.com wrote:
On Fri, Jul 10, 2009 at 4:57 AM, Robert
O'Callahanrob...@ocallahan.org wrote:
The way we've implemented in Firefox, we'll return
On Sat, Jul 11, 2009 at 5:23 AM, Aryeh Gregor
simetrical+...@gmail.comsimetrical%2b...@gmail.com
wrote:
Maybe you'd try testing all the video types you support, and
if one is maybe while another is probably you'd go with
probably?
Right. Or you might have plugin-based fallback you can use
On Sat, Jul 11, 2009 at 9:37 AM, Philip Jagenstedt phil...@opera.comwrote:
the point is simply that calling canPlayType without out a codecs list or
with specific codecs, you can learn exactly what is supported and not out of
the container formats and codecs you are interested in, without the
(this is not quite about the standard itself, but it is about how to
use shiny new bits of it in real world practice)
Wikimedia is preparing to use video (and quite likely HTML5 all
through) for serving up Ogg Theora video in MediaWiki.
Desktop is easy:
* In the one released browser that
David Gerard wrote:
* In the one released browser that supports video and Theora,
Firefox 3.5, this will Just Work.
Two! Firefox and Chrome.
--Ben
signature.asc
Description: OpenPGP digital signature
On Thu, Jul 9, 2009 at 10:04 PM, David Gerarddger...@gmail.com wrote:
Really? I thought that was next Chrome, not this Chrome.
It works in the developer version:
http://dev.chromium.org/getting-involved/dev-channel
Also in experimental Opera builds:
http://labs.opera.com/news/2008/11/25/
But
David Gerard wrote:
2009/7/9 Benjamin M. Schwartz bmsch...@fas.harvard.edu:
David Gerard wrote:
* In the one released browser that supports video and Theora,
Firefox 3.5, this will Just Work.
Two! Firefox and Chrome.
Really? I thought that was next Chrome, not this Chrome.
It seems
2009/7/9 David Gerard dger...@gmail.com:
* Everyone else gets the Cortado player (written in Java), with a link
suggesting FF 3.5 for a better video experience.
I should note, by the way, that this isn't a great option - second and
subsequent videos in Cortado are just fine, but the thirty
2009/7/9 Benjamin M. Schwartz bmsch...@fas.harvard.edu:
It seems you're rightish. Google, as usual, is having lots of fun with
their stable/beta/release distinctions. See if you can decipher
http://googlechromereleases.blogspot.com/ .
At any rate, video is not supported in Chrome Stable,
2009/7/9 Benjamin M. Schwartz bmsch...@fas.harvard.edu:
David Gerard wrote:
* In the one released browser that supports video and Theora,
Firefox 3.5, this will Just Work.
Two! Firefox and Chrome.
Really? I thought that was next Chrome, not this Chrome.
What's ETA on the next Chrome?
-
On Thu, Jul 9, 2009 at 5:59 PM, David Gerarddger...@gmail.com wrote:
* In Safari with XiphQT, we can *probably* detect Theora's MIME type
as being supported and it will Just Work (more or less).
I'm now being told that our workaround of checking for system mime
types stopped working and isn't
2009/7/9 David Gerard dger...@gmail.com
2009/7/9 Benjamin M. Schwartz bmsch...@fas.harvard.edu:
It seems you're rightish. Google, as usual, is having lots of fun with
their stable/beta/release distinctions. See if you can decipher
http://googlechromereleases.blogspot.com/ .
At any
On Thu, Jul 9, 2009 at 3:34 PM, David Gerarddger...@gmail.com wrote:
Anyone got ideas on the iPhone problem?
I think this is off topic, and I am not an iPhone developer, but:
Assuming the app store terms allow video players, it should be
possible to distribute some sort of dedicated player
2009/7/9 Ian Fette (イアンフェッティ) ife...@google.com:
As Peter said, please don't just block Chrome flat out -- if you must, just
block Chrome under version 3. Note that when we push 3 to stable, everyone
will be automatically updated.
As version 3 is easily detectable, presumably we'd just
On Jul 9, 2009, at 3:34 PM, Peter Kasting wrote:
On Thu, Jul 9, 2009 at 3:30 PM, Aryeh Gregor Simetrical
+...@gmail.com wrote:
On Thu, Jul 9, 2009 at 10:04 PM, David Gerarddger...@gmail.com
wrote:
Really? I thought that was next Chrome, not this Chrome.
It works in the developer version:
On Jul 9, 2009, at 3:11 PM, Gregory Maxwell wrote:
On Thu, Jul 9, 2009 at 5:59 PM, David Gerarddger...@gmail.com wrote:
* In Safari with XiphQT, we can *probably* detect Theora's MIME type
as being supported and it will Just Work (more or less).
I'm now being told that our workaround of
On Thu, Jul 9, 2009 at 7:14 PM, Maciej Stachowiakm...@apple.com wrote:
I don't think we did anything intentional in 4.0.2 to break detection of
XiphQT. If you have a solid reproducible case, please file a bug. On the
other hand, I suspect the canPlayType fix will have shipped by the time we
On Thu, Jul 9, 2009 at 7:24 PM, Maciej Stachowiakm...@apple.com wrote:
I thought your plan was to use Cortado for plugins that don't have
video+Theora. Why would you single out Safari users for a worse
experience?
As david mentioned, Cortado is a worse experience. What we've been
planning was
2009/7/10 Ian Fette (イアンフェッティ) ife...@google.com
To me, this seems like a great test if canPlayType actually works in
practice. In the perfect world, it would be great to do
getElementById('video'), createElement, and
then canPlayType('video/whatever','theora').
If this simple use case
On Thu, Jul 9, 2009 at 10:35 PM, Robert O'Callahanrob...@ocallahan.org wrote:
2009/7/10 Ian Fette (イアンフェッティ) ife...@google.com
To me, this seems like a great test if canPlayType actually works in
practice. In the perfect world, it would be great to do
getElementById('video'), createElement,
On Fri, Jul 10, 2009 at 2:46 PM, Gregory Maxwell gmaxw...@gmail.com wrote:
On Thu, Jul 9, 2009 at 10:35 PM, Robert O'Callahanrob...@ocallahan.org
wrote:
var v = document.getElementById(video);
if (v.canPlayType v.canPlayType(video/ogg; codecs=vorbis,theora)) {
...
} else {
...
On Jul 9, 2009, at 7:46 PM, Gregory Maxwell wrote:
On Thu, Jul 9, 2009 at 10:35 PM, Robert O'Callahanrob...@ocallahan.org
wrote:
2009/7/10 Ian Fette (イアンフェッティ) ife...@google.com
To me, this seems like a great test if canPlayType actually
works in
practice. In the perfect world, it would
On Jul 9, 2009, at 9:15 PM, Robert O'Callahan wrote:
On Fri, Jul 10, 2009 at 3:04 PM, Maciej Stachowiak m...@apple.com
wrote:
Robert's code is a bit buggy; canPlayType returns a string, not a
boolean, so it will always appear to say yes.
You're being polite, my code was not a bit buggy,
On Fri, Jul 10, 2009 at 3:04 PM, Maciej Stachowiak m...@apple.com wrote:
Robert's code is a bit buggy; canPlayType returns a string, not a boolean,
so it will always appear to say yes.
You're being polite, my code was not a bit buggy, it was completely
broken.
I've actually made this mistake
On Thu, 9 Jul 2009, Maciej Stachowiak wrote:
On Jul 9, 2009, at 9:15 PM, Robert O'Callahan wrote:
I actually anticipated this problem, and argued strenuously to break
canPlayType into two boolean functions, canPlayType and
cannotPlayType, but I lost. Hopefully most Web authors are
On Thu, Jul 9, 2009 at 9:22 PM, Maciej Stachowiakm...@apple.com wrote:
I think at one point I suggested that canPlayType should return one of
boolean false, true or maybe, so that naiive boolean tests would work. Or
in any case, make the no option something that tests as boolean false.
We
On Fri, Jul 10, 2009 at 4:40 PM, Ralph Giles gi...@xiph.org wrote:
To recap (off the top of my head): it's hard to say if you can play
something because that requires either a validator, or actually
playing it, So in addition to 'yes' and 'no', a 'maybe' was added, to
say I've heard of the
49 matches
Mail list logo
