Which version of MSE/EME spec is supported in chromium?

1,080 views
Skip to first unread message

David Landell

unread,
Jun 13, 2013, 6:08:08 AM6/13/13
to chromi...@chromium.org
Hi,

I am trying to figure out which version of Media Source Extension and
Encrypted Media Extension that is implemented in Chromium. I've seen
some stray comments regarding MSE version in the code, most of them
referring to the tip of the editor's draft.

Is there a way to find out which versions of these specifications
that is supported in a specific Chromium release?


Best regards,
David

--
David Landell
lan...@opera.com

Aaron Colwell

unread,
Jun 13, 2013, 10:51:51 AM6/13/13
to lan...@opera.com, Chromium-dev
Hi David,

The prefixed version MSE is essentially the October 8th version of the MSE spec plus the isTypeSupported() method from the current spec. I'm in the process of implementing the unprefixed version of the API that reflects the current spec. This initial patch should land sometime today and provides the same functionality as the prefixed API, but follows the current spec. I'll be rolling out further updates in the coming weeks that implement the various features that have been added to the spec since October 8th.

We've had support for the October 8th version of the spec since Chrome 23. WebKitMediaSource.isTypeSupported() was added in Chrome 27.

I'm not as familiar with the EME implementation, but I believe we currently support the 0.1b version of the spec. I believe work on an unprefixed version of the object-oriented API in the current spec is going on right now. ddo...@chromium.org is the guy to contact for more details on this front.

Aaron



--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
    http://groups.google.com/a/chromium.org/group/chromium-dev




David Landell

unread,
Jun 13, 2013, 12:52:12 PM6/13/13
to Aaron Colwell, Chromium-dev
Thanks Aaron,

Just the information I was looking for. I'd like to keep track of future
changes, past current spec implementation, if possible. Do you have any
recommended way of keeping track of this (main issue in bts or similar)
except bugging you from time to time?

David
--
David Landell
Developer, Devices Sweden
Opera Software

Aaron Colwell

unread,
Jun 13, 2013, 1:49:53 PM6/13/13
to David Landell, Chromium-dev
David,

Media Source related bugs are tracked with the Cr=Internals-Media-Source label(crbug query). Bug 239506 is tracking the unprefixed API implementation work. I need to associate all the subtasks with this bug, but that should be a good one to star to follow progress.

Aaron

David Dorwin

unread,
Jun 15, 2013, 12:06:33 AM6/15/13
to Aaron Colwell, David Landell, Chromium-dev
Hi David,

As Aaron said, Blink and Chromium currently have prefixed support for most of the 0.1b version of the Editor's Draft, and we are working on an unprefixed version of the current Editor's Draft. Bugs are tracked with the Cr=Internals-Media-Encrypted label.  Bug 224791 tracks the unrepfixed API implementation in Blink, and Bug 224786 tracks the Chromium side.

David
Reply all
Reply to author
Forward
0 new messages