Wake Lock API implementation (Blink part)

Source/modules/wake_lock/DocumentWakeLock.cpp

Index: Source/modules/wake_lock/DocumentWakeLock.cpp
diff --git a/Source/modules/wake_lock/DocumentWakeLock.cpp b/Source/modules/wake_lock/DocumentWakeLock.cpp
new file mode 100644
index 0000000000000000000000000000000000000000..0c06da4f13cf35b418038a3560f5df3044d2687a
--- /dev/null
+++ b/Source/modules/wake_lock/DocumentWakeLock.cpp
@@ -0,0 +1,22 @@
+// Copyright 2015 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "config.h"
+#include "modules/wake_lock/DocumentWakeLock.h"
+
+#include "modules/wake_lock/WakeLock.h"
+
+namespace blink {
+
+bool DocumentWakeLock::keepScreenAwake(Document& document)
+{
+    return WakeLock::keepScreenAwake(document);

[mlamouri (slow - plz ping), 2015/05/05 13:45:43]

Would it make sense to return false if document.frame() is null?

[alogvinov, 2015/05/05 16:22:27]

A web page could potentially create a detached document via
document.implementation.createHTMLDocument() and set keepScreenAwake flag on it,
then read it back, which works for the implementation presented here. This is
hardly useful, of course, but nevertheless possible. I will add a layout test to
the next CL to demonstrate it (and if we decide to use default value for
keepScreenAwake, we can modify this test accordingly to specify the behavior).

+}
+
+void DocumentWakeLock::setKeepScreenAwake(Document& document, bool keepScreenAwake)
+{
+    WakeLock::setKeepScreenAwake(document, keepScreenAwake);

[mlamouri (slow - plz ping), 2015/05/05 13:45:43]

Would it make sense to make it a no-op if document.frame() is null?

+}
+
+} // namespace blink