Implement <appview> skeleton.

chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc

Index: chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc
diff --git a/chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc b/chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc
index 08bc023906c2e53f5ed4ff9d4f86935f8492bb09..daebbe83ef9d716ccffe4a66b25bf90c304c5a90 100644
--- a/chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc
+++ b/chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc
@@ -235,6 +235,7 @@ void ChromeExtensionsDispatcherDelegate::PopulateSourceMap(
                              IDR_CHROME_DIRECT_SETTING_JS);
 
   // Platform app sources that are not API-specific..
+  source_map->RegisterSource("appView", IDR_APP_VIEW_JS);
   source_map->RegisterSource("tagWatcher", IDR_TAG_WATCHER_JS);
   source_map->RegisterSource("webViewInternal",
                              IDR_WEB_VIEW_INTERNAL_CUSTOM_BINDINGS_JS);
@@ -294,6 +295,14 @@ void ChromeExtensionsDispatcherDelegate::RequireAdditionalModules(
       module_system->Require("denyWebView");
     }
   }
+
+  if (context_type == extensions::Feature::BLESSED_EXTENSION_CONTEXT) {
+    if (CommandLine::ForCurrentProcess()->HasSwitch(switches::kEnableAppView) &&
+        extension->permissions_data()->HasAPIPermission(
+            extensions::APIPermission::kAppView)) {
+      module_system->Require("appView");
+    }

[not at google - send to devlin, 2014/06/27 17:32:19]

questions:
- why is this different logic to webview?
- what about "denyAppView"?
and please add a big todo somewhere; eagerly calling Request on context startup
is expensive, it would be better if there were a lightweight way of detecting
when an adview (or webview) is created and only then set up the infrastructure.
don't custom elements give you a way to do that?

this comment should go at the top of RequireAdditionalModels.

[Fady Samuel, 2014/06/27 18:14:31]

1. <webview> will work in unblessed contexts in the near feature (in component
extensions on WebUI pages). No immediate plans to support this for appview.
<webview> also has experimental features that are white listed. <appview> does
not.
Good point. Added.
I'm not sure how to do that but I can investigate in a separate patch.

[not at google - send to devlin, 2014/06/27 18:16:17]

So the "unblessed" isn't needed yet? can we take that out (in a separate CL)
because there are better ways to implement this for webui.
thanks.

+  }
 }
 
 void ChromeExtensionsDispatcherDelegate::OnActiveExtensionsUpdated(