<webview>: First stab at implementing media permission request for guests.

chrome/common/extensions/permissions/api_permission.h

Index: chrome/common/extensions/permissions/api_permission.h
diff --git a/chrome/common/extensions/permissions/api_permission.h b/chrome/common/extensions/permissions/api_permission.h
index 8a7038d0188c273872d09d181e5579a07df8bc0f..9c94e973f9cb141cd585e84b8aa56c058a3aad60 100644
--- a/chrome/common/extensions/permissions/api_permission.h
+++ b/chrome/common/extensions/permissions/api_permission.h
@@ -114,6 +114,7 @@ class APIPermission {
     kWebSocketProxyPrivate,
     kWebstorePrivate,
     kWebView,
+    kWebViewPermissionAPI,

[Charlie Reis, 2012/12/07 19:16:25]

Hmm, this requires developers to request a permission?  We don't want that in
the long term, right?  Perhaps we can just gate this stuff on kExperimental
instead?

[lazyboy, 2012/12/07 22:50:44]

Yes that requires permission and we don't want them in long term.
Looking at kExperimental, that is is marked as 'stable'
(chrome/common/extensions/api/_permission_features.json) and feels a bit too
broad for us.
Also we can rename this to kWebViewExperimental, so we use this as a bucket for
all experimental webview features.

[Charlie Reis, 2012/12/17 22:28:09]

Experimental is allowed in stable, but apps that use it can't be uploaded to the
web store, which accomplishes what we want.  I don't know if there's a similar
restriction for permissions marked dev.  If we did go this route,
kWebViewExperimental does seem like a more general name for future issues like
this.

Anyway, I'll defer on this, so please have someone from the apps team review it
to make sure they're ok with it.

[lazyboy, 2013/02/07 04:38:42]

Ah I see, 'experimental' should take care of our needs then.
Made web_view_experimental_api.js only served when 'experimental' permission is
available.

     kEnumBoundary
   };