Implement <webview>.addContentScript/removeContentScript API [1]

extensions/browser/user_script_loader.cc

Index: extensions/browser/user_script_loader.cc
diff --git a/extensions/browser/user_script_loader.cc b/extensions/browser/user_script_loader.cc
index c5b367c3b37d7b50ebf179e366c9c5884d3dd891..98a7b195e6b71d295f25d4c4c18e8705beeac774 100644
--- a/extensions/browser/user_script_loader.cc
+++ b/extensions/browser/user_script_loader.cc
@@ -475,10 +475,6 @@ void UserScriptLoader::OnScriptsLoaded(
 void UserScriptLoader::SendUpdate(content::RenderProcessHost* process,
                                   base::SharedMemory* shared_memory,
                                   const std::set<HostID>& changed_hosts) {
-  // Don't allow injection of content scripts into <webview>.
-  if (process->IsIsolatedGuest())

[Fady Samuel, 2015/03/11 11:50:19]

Are we sure this doesn't break things now? Content scripts from an extension
should not be in injected into webview.

[Xi Han, 2015/03/25 19:52:40]

I think we won't, since host_id is sent along with the IPC
ExtensionMsg_UpdateUserScripts. The host_id for content scripts of webview will
be a real extension_id or webui_id; while host_id of extension content scripts
will be an empty string.

-    return;
-
   // Make sure we only send user scripts to processes in our browser_context.
   if (!ExtensionsBrowserClient::Get()->IsSameContext(
           browser_context_, process->GetBrowserContext()))