Host Wake Lock Mojo interface in Device Service rather than //content/browser |
|||
Issue descriptionOnce the coupling to WebContents is removed (see blocking bug), it should be possible to have the Device Service host the Wake Lock Mojo interface rather than //content/browser. As part of this effort, the Mojo interface itself should be moved into //services/device/public/interfaces.
,
Jun 29 2017
The WakeLockProvider has already been hosted by Device Service. So set this bug's status as "fixed".
,
Nov 7 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by blundell@chromium.org
, Feb 7 2017