Remove RenderViewImpl::didActivateCompositor

Remove RenderViewImpl::didActivateCompositor

Everything is composited, so just move this code into initialization.

R=piman@chromium.org
BUG=none

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

[enne (OOO), 2014-05-21 22:53:56]

I apparently didn't clean this up enough in
https://codereview.chromium.org/288633002/

[piman, 2014-05-22 00:12:24]

https://codereview.chromium.org/296513010/diff/1/content/renderer/render_view...
File content/renderer/render_view_impl.cc (right):

https://codereview.chromium.org/296513010/diff/1/content/renderer/render_view...
content/renderer/render_view_impl.cc:739: compositor_->GetInputHandler(),
Do we have compositor_ this early? I thought it was created in CompleteInit. I
may be wrong though.

[enne (OOO), 2014-05-27 20:40:32]

https://codereview.chromium.org/296513010/diff/1/content/renderer/render_view...
File content/renderer/render_view_impl.cc (right):

https://codereview.chromium.org/296513010/diff/1/content/renderer/render_view...
content/renderer/render_view_impl.cc:739: compositor_->GetInputHandler(),
On 2014/05/22 00:12:24, piman OOO back 2014-6-09 wrote:
> Do we have compositor_ this early? I thought it was created in CompleteInit. I
> may be wrong though.

It's started in CompleteInit, but created in initializeLayerTreeView.  I think
you're right though that maybe Initialize() could happen prior to
initializeLayerTreeView and it seems safer to move this code there, where it's
100% sure that compositor_ now exists.

[piman, 2014-05-28 10:56:29]

lgtm

[enne (OOO), 2014-05-28 17:14:07]

The CQ bit was checked by enne@chromium.org

[commit-bot: I haz the power, 2014-05-28 17:15:33]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/enne@chromium.org/296513010/20001

[enne (OOO), 2014-05-28 17:37:51]

The CQ bit was unchecked by enne@chromium.org

[enne (OOO), 2014-05-28 18:07:23]

The CQ bit was checked by enne@chromium.org

[commit-bot: I haz the power, 2014-05-28 18:08:36]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/enne@chromium.org/296513010/40001

[commit-bot: I haz the power, 2014-05-28 21:57:22]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  android_dbg_triggered_tests on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_dbg_triggered...)
  linux_chromium_chromeos_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel/bu...)
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)

[commit-bot: I haz the power, 2014-05-28 22:42:18]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-05-28 22:42:18]

Try jobs failed on following builders:
  android_dbg_triggered_tests on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_dbg_triggered...)

[enne (OOO), 2014-05-29 20:14:09]

The CQ bit was checked by enne@chromium.org

[commit-bot: I haz the power, 2014-05-29 20:16:51]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/enne@chromium.org/296513010/60001

[commit-bot: I haz the power, 2014-05-30 00:41:47]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  android_aosp on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_aosp/builds/7...)
  linux_chromium_chromeos_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)

[commit-bot: I haz the power, 2014-05-30 01:51:19]

Change committed as 273695