Decouple WakeLock from direct //content dependencies

Decouple WakeLock from direct //content dependencies

As part of the Content Modularization Project, this CL removes direct
knowledge of //content from //content/browser's wake lock service.

The design follows that described here:

https://docs.google.com/document/d/1683obWqUStROtJHgkveAWbnGi-W3P7gMylzYeImEzBU/edit#heading=h.jr0fqceqrud1

Note that this CL does not remove synchronous dependencies of this code
on //content: on Android a callback is passed in in order to obtain
the current NativeView when creating a wake lock. I do not know how to
remove that dependency at this time: WebContent::GetNativeView() can
return different values throughout the lifetime of a WebContents instance,
at least on Android.

Two unittests were removed from wake_lock_service_context.cc as they are not
relevant at the //device level. The functionality of render frame deletion is
still tested via the browsertest.

BUG=612346
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Committed: https://crrev.com/ebd751770f62eb05586897f4d2843f2c0d8af0b9
Cr-Commit-Position: refs/heads/master@{#422397}

[blundell, 2016-09-28 13:29:13]

Description was changed from

==========
Decouple WakeLock from direct //content dependencies

As part of the Content Modularization Project, this CL removes direct
knowledge of //content from //content/browser's wake lock service.

The design follows that described here:

https://docs.google.com/document/d/1683obWqUStROtJHgkveAWbnGi-W3P7gMylzYeImEz...

Note that this CL does not remove synchronous dependencies of this code
on //content: on Android a callback is passed in in order to obtain
the current NativeView when creating a wake lock. I do not know how to
remove that dependency at this time: WebContent::GetNativeView() can
return different values throughout the lifetime of a WebContents instance,
at least on Android.

Two unittests were removed from wake_lock_service_context.cc as they are not
relevant at the //device level. The functionality of render frame deletion is
still tested via the browsertest.

BUG=612346
==========

to

==========
Decouple WakeLock from direct //content dependencies

As part of the Content Modularization Project, this CL removes direct
knowledge of //content from //content/browser's wake lock service.

The design follows that described here:

https://docs.google.com/document/d/1683obWqUStROtJHgkveAWbnGi-W3P7gMylzYeImEz...

Note that this CL does not remove synchronous dependencies of this code
on //content: on Android a callback is passed in in order to obtain
the current NativeView when creating a wake lock. I do not know how to
remove that dependency at this time: WebContent::GetNativeView() can
return different values throughout the lifetime of a WebContents instance,
at least on Android.

Two unittests were removed from wake_lock_service_context.cc as they are not
relevant at the //device level. The functionality of render frame deletion is
still tested via the browsertest.

BUG=612346
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation
==========

[blundell, 2016-09-28 13:31:30]

The CQ bit was checked by blundell@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-09-28 13:31:38]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-28 14:16:23]

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

[commit-bot: I haz the power, 2016-09-28 14:16:24]

Dry run: This issue passed the CQ dry run.

[blundell, 2016-09-28 14:18:41]

blundell@chromium.org changed reviewers:
+ alogvinov@yandex-team.ru, jam@chromium.org

[jam, 2016-09-29 20:08:50]

lgtm

[alogvinov, 2016-09-30 09:15:30]

lgtm

lgtm

[alogvinov, 2016-09-30 09:15:34]

lgtm

[blundell, 2016-10-03 09:29:53]

The CQ bit was checked by blundell@chromium.org

[commit-bot: I haz the power, 2016-10-03 09:30:12]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-03 10:42:07]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-10-03 10:44:20]

Description was changed from

==========
Decouple WakeLock from direct //content dependencies

As part of the Content Modularization Project, this CL removes direct
knowledge of //content from //content/browser's wake lock service.

The design follows that described here:

https://docs.google.com/document/d/1683obWqUStROtJHgkveAWbnGi-W3P7gMylzYeImEz...

Note that this CL does not remove synchronous dependencies of this code
on //content: on Android a callback is passed in in order to obtain
the current NativeView when creating a wake lock. I do not know how to
remove that dependency at this time: WebContent::GetNativeView() can
return different values throughout the lifetime of a WebContents instance,
at least on Android.

Two unittests were removed from wake_lock_service_context.cc as they are not
relevant at the //device level. The functionality of render frame deletion is
still tested via the browsertest.

BUG=612346
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation
==========

to

==========
Decouple WakeLock from direct //content dependencies

As part of the Content Modularization Project, this CL removes direct
knowledge of //content from //content/browser's wake lock service.

The design follows that described here:

https://docs.google.com/document/d/1683obWqUStROtJHgkveAWbnGi-W3P7gMylzYeImEz...

Note that this CL does not remove synchronous dependencies of this code
on //content: on Android a callback is passed in in order to obtain
the current NativeView when creating a wake lock. I do not know how to
remove that dependency at this time: WebContent::GetNativeView() can
return different values throughout the lifetime of a WebContents instance,
at least on Android.

Two unittests were removed from wake_lock_service_context.cc as they are not
relevant at the //device level. The functionality of render frame deletion is
still tested via the browsertest.

BUG=612346
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Committed: https://crrev.com/ebd751770f62eb05586897f4d2843f2c0d8af0b9
Cr-Commit-Position: refs/heads/master@{#422397}
==========

[commit-bot: I haz the power, 2016-10-03 10:44:21]

Patchset 1 (id:??) landed as
https://crrev.com/ebd751770f62eb05586897f4d2843f2c0d8af0b9
Cr-Commit-Position: refs/heads/master@{#422397}