Remove HTMLVideoElement.

Remove HTMLVideoElement.

This also removes some compositor related code, but there's not much of
it anyway so we can just add it back later when we do <iframe>.

R=ojan@chromium.org, abarth@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/3c577b6f465a01b2e9f16a3634242d99ba289f43

[ojan, 2014-11-03 23:53:04]

ojan@chromium.org changed reviewers:
+ ojan@chromium.org

[ojan, 2014-11-03 23:53:05]

In the future world, how will you do image processing of a video the way you
used to with canvas? I guess you can't? You have to do it on the other side of
the mojo pipe?

[esprehn, 2014-11-04 00:53:29]

On 2014/11/03 at 23:53:05, ojan wrote:
> In the future world, how will you do image processing of a video the way you
used to with canvas? I guess you can't? You have to do it on the other side of
the mojo pipe?

What do you mean? <canvas> could render a static image of a single frame from
the <video>, we can expose such an API on the video player mojo API, you'd do
something like <iframe src="foo.mp4" id="video"> and then connect to the
VideoPlayer mojo service and call captureFrame(time) or something?

[abarth-chromium, 2014-11-04 01:05:35]

On 2014/11/04 at 00:53:29, esprehn wrote:
> On 2014/11/03 at 23:53:05, ojan wrote:
> > In the future world, how will you do image processing of a video the way you
used to with canvas? I guess you can't? You have to do it on the other side of
the mojo pipe?
> 
> What do you mean? <canvas> could render a static image of a single frame from
the <video>, we can expose such an API on the video player mojo API, you'd do
something like <iframe src="foo.mp4" id="video"> and then connect to the
VideoPlayer mojo service and call captureFrame(time) or something?

That code doesn't exist today, but something like that could work.

[ojan, 2014-11-04 02:01:52]

lgtm

[esprehn, 2014-11-04 02:02:28]

Committed patchset #1 (id:1) manually as
3c577b6f465a01b2e9f16a3634242d99ba289f43.