Rationalize WakeLock naming conventions
This CL makes some changes of the WakeLock naming conventions.
WakeLockService -> WakeLock
Drop the "Impl" from "WakeLockServiceImpl"
BUG=701414
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation
Review-Url: https://codereview.chromium.org/2921823002
Cr-Commit-Position: refs/heads/master@{#477400}
diff --git a/content/browser/web_contents/web_contents_impl.cc b/content/browser/web_contents/web_contents_impl.cc
index 99cfc118..d9681451 100644
--- a/content/browser/web_contents/web_contents_impl.cc
+++ b/content/browser/web_contents/web_contents_impl.cc
@@ -2643,10 +2643,10 @@
return wake_lock_context_host_->GetWakeLockContext();
}
-device::mojom::WakeLockService* WebContentsImpl::GetRendererWakeLock() {
- // WebContents creates a long-lived connection to one WakeLockServiceImpl.
+device::mojom::WakeLock* WebContentsImpl::GetRendererWakeLock() {
+ // WebContents creates a long-lived connection to one WakeLock.
// All the frames' requests will be added into the BindingSet of
- // WakeLockServiceImpl via this connection.
+ // WakeLock via this connection.
if (!renderer_wake_lock_) {
device::mojom::WakeLockContext* wake_lock_context = GetWakeLockContext();
if (!wake_lock_context) {
