Use different client interface for WebLayerTreeViewForTesting to decouple from WebLayerTreeViewClie…

Use different client interface for WebLayerTreeViewForTesting to decouple from WebLayerTreeViewClient

WebLayerTreeView when used in production (i.e. be content) has different requirements
from DumpRenderTree. In DRT, we need to route two calls from the compositor into
DRT - Layout() and ScheduleComposite(). Neither are needed in the non-DRT
embedding of WebLayerTreeView. This introduces a new client interface for DRT to
use that only has these two functions. I've left the old path in place to keep
things from breaking until the WebKit change rolls in, after that point I'll
remove the WebLayerTreeViewClient references from WebLayerTreeViewImplForTesting
completely.

R=enne@chromium.org

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

[jamesr, 2013-02-27 22:59:50]

This stuff is crazy.  WebKit side is
https://bugs.webkit.org/show_bug.cgi?id=111017, has to land after this.

[enne (OOO), 2013-02-28 18:17:43]

lgtm

[commit-bot: I haz the power, 2013-02-28 19:01:37]

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

[commit-bot: I haz the power, 2013-02-28 21:59:04]

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

[jamesr, 2013-02-28 22:09:08]

Committed patchset #1 manually as r185341 (presubmit successful).