W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2012

[Bug 19531] simplify MIME type capability detection

From: <bugzilla@jessica.w3.org>
Date: Mon, 15 Oct 2012 20:38:48 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-19531-2486-viSMy2eBMA@http.www.w3.org/Bugs/Public/>

Aaron Colwell <acolwell@chromium.org> changed:

           What    |Removed                     |Added
                 CC|                            |acolwell@chromium.org

--- Comment #2 from Aaron Colwell <acolwell@chromium.org> ---
(In reply to comment #1)
> http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.
> html#byte-stream-formats says
> "Byte stream format specifications based on WebM and the ISO Base Media File
> Format are provided below. If these formats are supported then the byte
> stream formats described below must be supported."
> In other words, the spec requires that if you support WebM in plain <video>,
> then you must also support it using MSE. This means that you can just use
> HTMLMediaElement.canPlayType(), which is synchronous.

That wasn't my original intent when I wrote that. My original intent was "if
you want to support WebM in MSE, then you must follow the rules that are
outlined below". I didn't mean to imply that if canPlayType() indicates WebM
support then the MSE implementation must support the associated bytestream as

We can make that requirement explicit if people think that is the best path.
I'm a little concerned that this would prevent UA's from incrementally adding
support for different bytestream formats. If a UA supports both WebM & MP4 then
they would have to add MediaSource support for both before exposing any MSE
functionality. Chrome rolled out WebM-only support first and then eventually
added MP4 later. I would assume that other UA's might want to follow a similar

I was planning on responding to this bug with something along the lines of the

partial interface MediaSource {
  static bool isTypeSupported(DOMString type);

True would be returned if the UA is able to create a SourceBuffer for the
specified type. This seemed a little more explicit than what canPlayType()

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 15 October 2012 20:38:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:34 UTC