Hi,
as it looks like there will not be a common base codec any time soon,
there is a need to be able to detect the supported codecs in javascript.
are there any plans to provide such an interface or is this already
possible?
j
On Wed, 18 Jun 2008 12:01:13 +0200, [EMAIL PROTECTED] wrote:
as it looks like there will not be a common base codec any time soon,
there is a need to be able to detect the supported codecs in javascript.
are there any plans to provide such an interface or is this already
possible?
Why is that
On Wed, 2008-06-18 at 12:03 +0200, Anne van Kesteren wrote:
Why is that needed? The elements provide a way to link to multiple codecs
of which the user agent will then make a choice.
i do not intend to provide multiple codecs since that would require
multiple backend implementations for
It seems to me that it's a good idea to wait with this until we know
more about what will happen with baseline codecs etc.
Implementation-wise it might be less than trivial to return an
exhaustive list of all supported mime-types if the underlying framework
doesn't use the concept of mime-types,
Sorry, my reply was cut short. Again:
It seems to me that it's a good idea to wait with this until we know
more about what will happen with baseline codecs etc.
Implementation-wise it might be less than trivial to return an
exhaustive list of all supported mime-types if the underlying framework
The spec clearly says the following
http://www.whatwg.org/specs/web-apps/current-work/#video1
User agents should not show this content to the user; it is intended
for older Web browsers which do not support video,
Although we fully understand the reasoning behind this, there's an use
case
On Wed, 2008-06-18 at 17:38 +0700, Philip Jägenstedt wrote:
Implementation-wise it might be less than trivial to return an
exhaustive list of all supported mime-types if the underlying framework
doesn't use the concept of mime-types, but can say when given a few
bytes of the file whether it
On Jun 18, 2008, at 13:34, Philip Jägenstedt wrote:
Implementation-wise it might be less than trivial to return an
exhaustive list of all supported mime-types if the underlying
framework
doesn't use the concept of mime-types, but can say when given a few
bytes of the file whether it supports
