This e-mail is a reply to two threads asking for a way to see if a type is
supported. As with the earlier thread on the same topic, it is something
that I think would be good if we could provide it, but my understanding is
that it isn't something that is realistically going to be reliably
On Tue, Oct 14, 2008 at 12:10 PM, Ian Hickson [EMAIL PROTECTED] wrote:
Try to play all the videos you have available, and catch errors:
video id=a
source src=video.mp4 type=video/mp4; codecs=quot;avc1.42E01E,
mp4a.40.2quot;
source src=video.3gp type=video/3gpp; codecs=quot;mp4v.20.8,
Perhaps another possibility would be something similar to the current
navigagor.mimeTypes array (navigator.mediaMimeTypes?). Absolutely
old-school, but perhaps makes sense, as the ability to display certain
media types is mostly a property of the navigator/client, not as much
a property of the
For some strange definition of lie. You're defining a lie as ok and
saying it isn't lying.
i still don't see why this is valuable. Can you provide use cases
where you won't harm my users? This probably means setting up a web
page which explains what you're doing and how you're going to fall
back
On Sat, Aug 23, 2008 at 2:17 PM, Tim Starling [EMAIL PROTECTED]wrote:
With this proposal, I'm trying to find a compromise between the opinions
put forward on this list. Personally I'd be happy either way, as long as
the interface gets added in some form.
The yes = maybe definition pre-empts
On Aug 21, 2008, at 8:56 PM, Robert O'Callahan wrote:
On Fri, Aug 22, 2008 at 2:57 PM, Eric Carlson
[EMAIL PROTECTED] wrote:
It is possible to build a list of all types supported by QuickTime
dynamically. WebKit does this, so Safari knows about both the built
in types and those added by
On Sat, Aug 23, 2008 at 1:46 AM, Eric Carlson [EMAIL PROTECTED]wrote:
On Aug 21, 2008, at 8:56 PM, Robert O'Callahan wrote:
Does that actually enumerate all supported codecs? Looking at the Webkit
code and the Quicktime docs, it looks like it's just enumerating
file/container types.
On Aug 22, 2008, at 2:36 PM, Robert O'Callahan wrote:
On Sat, Aug 23, 2008 at 1:46 AM, Eric Carlson
[EMAIL PROTECTED] wrote:
On Aug 21, 2008, at 8:56 PM, Robert O'Callahan wrote:
Does that actually enumerate all supported codecs? Looking at the
Webkit code and the Quicktime docs, it
On Sat, Aug 23, 2008 at 11:21 AM, Eric Carlson [EMAIL PROTECTED]wrote:
A three state return is an interesting idea, but wouldn't you then be
required to return maybe for MIME types that can describe multiple
formats? For example, video/mpeg can be used to describe a video
elementary
interface HTMLMediaElement {
...
boolean supportsType(in DOMString type);
...
}
The supportsType() method must return false if the user agent is sure it
cannot support the given type, and true if the user agent either can
support the given type, or cannot determine whether it can
On Aug 21, 2008, at 7:46 PM, Robert O'Callahan wrote:
Any browser that supports integration with an extensible framework
like GStreamer, Quicktime or Direct Show is going to have a hard
time ever reporting false. Apparently there was a conversation
today in #theora that you might have
On Fri, Aug 22, 2008 at 2:57 PM, Eric Carlson [EMAIL PROTECTED]wrote:
It is possible to build a list of all types supported by QuickTime
dynamically. WebKit does this, so Safari knows about both the built in types
and those added by third party importers.
You mean this
12 matches
Mail list logo
