Enable builtin Mojo JS modules in layout tests

content/public/common/bindings_policy.h

 // Copyright (c) 2012 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.
 
 #ifndef CONTENT_PUBLIC_COMMON_BINDINGS_POLICY_H_
 #define CONTENT_PUBLIC_COMMON_BINDINGS_POLICY_H_
 
 namespace content {
 
 // This enum specifies flag values for the types of JavaScript bindings exposed
 // to renderers.
 enum BindingsPolicy {
   // HTML-based UI bindings that allows the JS content to send JSON-encoded
   // data back to the browser process.
   BINDINGS_POLICY_WEB_UI = 1 << 0,
   // DOM automation bindings that allows the JS content to send JSON-encoded
   // data back to automation in the parent process.  (By default this isn't
   // allowed unless the app has been started up with the --dom-automation
   // switch.)
   BINDINGS_POLICY_DOM_AUTOMATION = 1 << 1,
   // Bindings that allows the JS content to retrieve a variety of internal
   // metrics. (By default this isn't allowed unless the app has been started up
   // with the --enable-stats-collection-bindings switch.)
   BINDINGS_POLICY_STATS_COLLECTION = 1 << 2,
+  // Bindings that allows the JS context to access Mojo EDK modules and use a

[Charlie Reis, 2016/01/15 01:26:51]

Please elaborate what EDK means in the comment.  I don't think most content/
folks (myself included) know what it is.

[Ken Rockot(use gerrit already), 2016/01/24 23:03:51]

Done.

+  // ServiceRegistry to connect to browser or test Mojo services.
+  BINDINGS_POLICY_MOJO = 1 << 3,
 
 };
 
 }
 
 #endif  // CONTENT_PUBLIC_COMMON_BINDINGS_POLICY_H_