Remove content/browser/power_save_blocker_factory.*

Remove content/browser/power_save_blocker_factory.*

Followup to https://codereview.chromium.org/1999953002. Just inline the creation
call rather than having a separate factory function.

R=jam@chromium.org
BUG=612337, 612563
Committed: https://crrev.com/90f7c1198c9c1ceb406834061b31f8f980b672ea
Cr-Commit-Position: refs/heads/master@{#400534}

[jam, 2016-06-17 22:11:58]

https://codereview.chromium.org/2072403002/diff/20001/content/browser/wake_lo...
File content/browser/wake_lock/wake_lock_service_context.cc (right):

https://codereview.chromium.org/2072403002/diff/20001/content/browser/wake_lo...
content/browser/wake_lock/wake_lock_service_context.cc:71: wake_lock_ =
device::PowerSaveBlocker::CreateWithTaskRunners(
can we also get rid of this method?

what about the interface and impl as well? we only had that separation because
of the content api. we don't need that anymore.

[scottmg, 2016-06-17 22:17:27]

On 2016/06/17 22:11:58, jam wrote:
>
https://codereview.chromium.org/2072403002/diff/20001/content/browser/wake_lo...
> File content/browser/wake_lock/wake_lock_service_context.cc (right):
> 
>
https://codereview.chromium.org/2072403002/diff/20001/content/browser/wake_lo...
> content/browser/wake_lock/wake_lock_service_context.cc:71: wake_lock_ =
> device::PowerSaveBlocker::CreateWithTaskRunners(
> can we also get rid of this method?
> 
> what about the interface and impl as well? we only had that separation because
> of the content api. we don't need that anymore.

Yup, coming in the next CL.

[scottmg, 2016-06-17 22:28:33]

On 2016/06/17 22:17:27, scottmg wrote:
> On 2016/06/17 22:11:58, jam wrote:
> >
>
https://codereview.chromium.org/2072403002/diff/20001/content/browser/wake_lo...
> > File content/browser/wake_lock/wake_lock_service_context.cc (right):
> > 
> >
>
https://codereview.chromium.org/2072403002/diff/20001/content/browser/wake_lo...
> > content/browser/wake_lock/wake_lock_service_context.cc:71: wake_lock_ =
> > device::PowerSaveBlocker::CreateWithTaskRunners(
> > can we also get rid of this method?
> > 
> > what about the interface and impl as well? we only had that separation
because
> > of the content api. we don't need that anymore.
> 
> Yup, coming in the next CL.

Removing CreateWithTaskRunners() and collapsing interface and impl is here:
https://codereview.chromium.org/2073353002.

[jam, 2016-06-17 22:29:09]

lgtm

[scottmg, 2016-06-17 22:32:10]

The CQ bit was checked by scottmg@chromium.org

[commit-bot: I haz the power, 2016-06-17 22:32:23]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2072403002/40001

[commit-bot: I haz the power, 2016-06-17 23:08:13]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-06-17 23:09:45]

Description was changed from

==========
Remove content/browser/power_save_blocker_factory.*

Followup to https://codereview.chromium.org/1999953002. Just inline the creation
call rather than having a separate factory function.

R=jam@chromium.org
BUG=612337,612563
==========

to

==========
Remove content/browser/power_save_blocker_factory.*

Followup to https://codereview.chromium.org/1999953002. Just inline the creation
call rather than having a separate factory function.

R=jam@chromium.org
BUG=612337,612563

Committed: https://crrev.com/90f7c1198c9c1ceb406834061b31f8f980b672ea
Cr-Commit-Position: refs/heads/master@{#400534}
==========

[commit-bot: I haz the power, 2016-06-17 23:09:46]

Patchset 3 (id:??) landed as
https://crrev.com/90f7c1198c9c1ceb406834061b31f8f980b672ea
Cr-Commit-Position: refs/heads/master@{#400534}