Implement the wake-event-page internal extension API.

This is implemented purely using IPC because it will be used from worker
contexts, which don't have access to extension bindings. The next step will be
to add worker thread support so the renderer side is structured to easily
accommodate for that, once the public content API is chaned to allow it.

It will be used in the public chrome.runtime.getBackgroundClient() exposed to
service workers.

BUG=501569
R=rdevlin.cronin@chromium.org, palmer@chromium.org

Review URL: https://codereview.chromium.org/1294993004

Cr-Commit-Position: refs/heads/master@{#344834}

1 files changed, 5 insertions, 0 deletions

diff --git a/extensions/renderer/resources/test_custom_bindings.js b/extensions/renderer/resources/test_custom_bindings.js
index ebb3f1b..7310f06 100644
--- a/extensions/renderer/resources/test_custom_bindings.js
+++ b/extensions/renderer/resources/test_custom_bindings.js
@@ -11,6 +11,7 @@ var environmentSpecificBindings = require('test_environment_specific_bindings');
 var GetExtensionAPIDefinitionsForTest =
     requireNative('apiDefinitions').GetExtensionAPIDefinitionsForTest;
 var GetAPIFeatures = requireNative('test_features').GetAPIFeatures;
+var natives = requireNative('test_native_handler');
 var uncaughtExceptionHandler = require('uncaught_exception_handler');
 var userGestures = requireNative('user_gestures');
 
@@ -353,6 +354,10 @@ binding.registerCustomHook(function(api) {
     uncaughtExceptionHandler.setHandler(callback);
   });
 
+  apiFunctions.setHandleRequest('getWakeEventPage', function() {
+    return natives.GetWakeEventPage();
+  });
+
   environmentSpecificBindings.registerHooks(api);
 });