Initial implementation of API WakeLock.

Source/modules/wake_lock/WakeLock.idl

Index: Source/modules/wake_lock/WakeLock.idl
diff --git a/Source/modules/wake_lock/WakeLock.idl b/Source/modules/wake_lock/WakeLock.idl
new file mode 100644
index 0000000000000000000000000000000000000000..befd840ad6af2f1be78b30b565507fa9b2ba3057
--- /dev/null
+++ b/Source/modules/wake_lock/WakeLock.idl
@@ -0,0 +1,18 @@
+// Copyright 2014 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.
+
+enum WakeLockType {
+    "screen",
+    "system"

[mlamouri (slow - plz ping), 2014/08/18 12:15:53]

Do you intend to implement "system"? Should we stick with "screen" for the
moment? We should consider how to behave if we support "screen" but not
"system": should we reject "system" as an unknown keyword or reject it as known
but unsupported?

[redchenko, 2014/08/19 16:42:20]

Yes we do, as Chromium's PowerSaveBlocker already has the code for that.

+};
+
+[
+    RuntimeEnabled=WakeLock,
+    WillBeGarbageCollected,
+    NoInterfaceObject,

[mlamouri (slow - plz ping), 2014/08/18 12:15:53]

Why is that NoInterfaceObject? It's unlikely what we want.

[redchenko, 2014/08/19 16:42:20]

Done.

+] interface WakeLock {
+    [CallWith=ScriptState] Promise request(WakeLockType type);
+    [CallWith=ScriptState] Promise release(WakeLockType type);
+    boolean isHeld(WakeLockType type);

[mlamouri (slow - plz ping), 2014/08/18 12:15:52]

Should you add an event handler for when the lock changes?

[redchenko, 2014/08/19 16:42:20]

Right, I'm planning it in the next CLs. Also there are questions about event
types we need.

+};