Add WebKit prefix to MediaSource,SourceBuffer, and SourceBufferList objects.

Add WebKit prefix to MediaSource,SourceBuffer, and SourceBufferList objects.

The current MediaSource API implementation is prefixed from JavaScript's point
of view, but is not in the C++ code. I plan to implement an unprefixed version
of the MediaSource API that is consistent with the current spec. The prefixed
version needs to be moved aside to make room for the unprefixed version which
will be quite different because of significant changes to the spec over the last
6 months. 

These objects are also being migrated to a new runtime flag to make it possible to
enable/disable the prefixed and unprefixed versions independently.

BUG=239485
TEST=No new tests since this is just a class rename.
R=eseidel@chromium.org

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=150131

[acolwell GONE FROM CHROMIUM, 2013-05-09 17:17:42]

Intent to Implement for unprefixed MediaSource API will be coming shortly. This
just moves the existing prefixed API out of the way so that it will be easier to
see/review what is new with the unprefixed API.

[eseidel, 2013-05-09 20:05:22]

lgtm

This is going to get confusing fast. :)  Just like how notifications vs. legacy
notifiations are today.

Do we have a removal plan for this prefixed version?  Ideally we'd like to
remove it from that platform as soon as that's feasible.

https://codereview.chromium.org/14619016/diff/1/Source/core/page/DOMWindow.idl
File Source/core/page/DOMWindow.idl (right):

https://codereview.chromium.org/14619016/diff/1/Source/core/page/DOMWindow.id...
Source/core/page/DOMWindow.idl:303: [EnabledAtRuntime=webKitMediaSource]
attribute WebKitMediaSourceConstructor WebKitMediaSource;
I suspect this could move into a supplement these days?

[commit-bot: I haz the power, 2013-05-09 20:05:31]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/acolwell@chromium.org/14619016/1

[commit-bot: I haz the power, 2013-05-09 20:09:45]

Retried try job too often on blink_bare_presubmit for step(s) presubmit
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=blink_bare...

[acolwell GONE FROM CHROMIUM, 2013-05-09 20:23:41]

On 2013/05/09 20:05:22, Eric Seidel wrote:
> lgtm
> 
> This is going to get confusing fast. :)  Just like how notifications vs.
legacy
> notifiations are today.
> 
> Do we have a removal plan for this prefixed version?  Ideally we'd like to
> remove it from that platform as soon as that's feasible.

Yes. The goal is to get the unprefixed version to feature parity + some of the
extra features so that sites are motivated to quickly migrate off of the
prefixed version. Netflix & YouTube have deployed with the prefixed API so we
are at least stuck w/ it for 3 more versions of Chrome.

> https://codereview.chromium.org/14619016/diff/1/Source/core/page/DOMWindow.idl
> File Source/core/page/DOMWindow.idl (right):
> 
>
https://codereview.chromium.org/14619016/diff/1/Source/core/page/DOMWindow.id...
> Source/core/page/DOMWindow.idl:303: [EnabledAtRuntime=webKitMediaSource]
> attribute WebKitMediaSourceConstructor WebKitMediaSource;
> I suspect this could move into a supplement these days?

I'm not sure what you mean.

[acolwell GONE FROM CHROMIUM, 2013-05-09 20:50:28]

jamesr@ : Can I please have an OWNERS lgtm for 	 Source/WebKit/chromium/public
changes.

[jamesr, 2013-05-09 20:51:54]

Eric's an OWNER for WebRuntimeFeatures.h

[acolwell GONE FROM CHROMIUM, 2013-05-09 20:59:39]

On 2013/05/09 20:51:54, jamesr wrote:
> Eric's an OWNER for WebRuntimeFeatures.h

Hmm.. it looks like presubmit used by the CQ doesn't agree. I'll try landing
manually.

[jamesr, 2013-05-09 21:03:26]

That should work.  Any idea why the presubmit doesn't like eseidel's review on
this patch, Dirk?

[Dirk Pranke, 2013-05-09 21:08:26]

On 2013/05/09 21:03:26, jamesr wrote:
> That should work.  Any idea why the presubmit doesn't like eseidel's review on
> this patch, Dirk?

The OWNERS file has "per-file (WebRuntimeFeatures.*)=eseidel@chromium.org" .

I don't think the parentheses will work; I think the open and close parens will
be treated as literals and not metacharacters.

[commit-bot: I haz the power, 2013-05-09 21:45:46]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/acolwell@chromium.org/14619016/13001

[commit-bot: I haz the power, 2013-05-10 03:49:42]

Retried try job too often on mac_layout for step(s) webkit_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_layout...

[commit-bot: I haz the power, 2013-05-10 14:15:44]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/acolwell@chromium.org/14619016/13001

[commit-bot: I haz the power, 2013-05-10 20:31:13]

Retried try job too often on win_layout for step(s) webkit_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_layout...

[acolwell GONE FROM CHROMIUM, 2013-05-10 20:34:22]

Committed patchset #3 manually as r150131 (presubmit successful).