Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(59)

Side by Side Diff: device/wake_lock/public/interfaces/wake_lock_service.mojom

Issue 2843353003: Move ownership of PowerSaveBlocker from WakeLockServiceContext to WakeLockServiceImpl (Closed)
Patch Set: error fix, non-frame client. Created 3 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 // Copyright 2015 The Chromium Authors. All rights reserved. 1 // Copyright 2015 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 module device.mojom; 5 module device.mojom;
6 6
7 // WebLockService receives wake lock preferences from its client. 7 // WebLockService receives wake lock preferences from its client.
8 interface WakeLockService { 8 interface WakeLockService {
9 RequestWakeLock(); 9 RequestWakeLock();
10 CancelWakeLock(); 10 CancelWakeLock();
11
12 // TODO(heke): The AddClient() interface is only used by WebContents for the
blundell 2017/05/02 11:27:43 Actually, I think it's fine to leave this method o
ke.he 2017/05/04 11:54:14 Yes, Totally understand after the mail discussion.
13 // purpose of coalescing requests from frames. It is better to split it into
14 // a seperate mojo interface and refactor WakeLockServiceContext and
15 // WakeLockServiceImpl accordingly.
16 AddClient(WakeLockService& wake_lock);
11 }; 17 };
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698