Avoid going through WebWidget::composite to composite a RenderWidget

Avoid going through WebWidget::composite to composite a RenderWidget

When a content::RenderWidget is using accelerated compositing, the compositing
is driven either by a WebLayerTreeView owned by the RenderWidget or a PepperWidget
if the RenderWidget is actually a RenderWidgetFullscreenPepper. Neither case
involves WebKit, so this avoids calling WebWidget::composite in favor of directly
calling in to the appropriate compositing system.

BUG=


Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=178746

[jamesr, 2013-01-04 22:20:10]

This depends on https://codereview.chromium.org/11575049/.  Once both land, the
WebKit::WebWidget::composite() API will go away completely.

Manually tested by playing a flash youtube video and taking it fullscreen (on
linux with --ignore-gpu-blacklist so flash uses the 3d path).

[brettw, 2013-01-04 22:22:25]

lgtm

https://codereview.chromium.org/11787006/diff/1/content/renderer/render_widge...
File content/renderer/render_widget_fullscreen_pepper.cc (right):

https://codereview.chromium.org/11787006/diff/1/content/renderer/render_widge...
content/renderer/render_widget_fullscreen_pepper.cc:505: void
RenderWidgetFullscreenPepper::Composite() {
Can you put a comment here "We need to override the default compositing of
RenderView because it has a thing that does the thing with the stuff and we want
the other stuff with the other thing." Feel free to clarify :)

[nduca, 2013-01-05 00:32:55]

This is awesome. Also, I think we should totally use the comment text suggested
by brett, verbatim.

[commit-bot: I haz the power, 2013-01-25 01:49:34]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jamesr@chromium.org/11787006/4001

[commit-bot: I haz the power, 2013-01-25 04:38:16]

Change committed as 178746