New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 878158 link

Starred by 1 user
Status: Assigned
Owner:
rdevlin....@chromium.org
Cc:
markchang@chromium.org
█ lottie@chromium.org
█ konsto@chromium.org
jawag@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Feature



Sign in to add a comment

New extension API: getAllPermissions given the extension / app ID.

Project Member Reported by lottie@chromium.org, Aug 27 
This is a feature request from the Chrome Web Store team. We'd like to display extension permissions so that users are aware before attempt to install. To ensure we always display the correct human readable permissions, we must reply on the Chrome browser.

Therefore we request an extension API for CWS (or public) to return a list of strings, each string is a line of permission description, ordered by the power of the permission. 

CWS can provide the extensions ID and the manifest as input. Optionally we will provide an hl field indicating the language used on the current website.

Comment 1 by rdevlin....@chromium.org, Aug 27

Cc: lottie@chromium.org jawag@chromium.org
Components: Platform>Extensions Webstore
Labels: -Extensions -cws -crx OS-Chrome OS-Linux OS-Mac OS-Windows
Status: Assigned (was: Untriaged)
Thinking about this, we already have management.getPermissionWarningsByManifest() [1] - would that just about work for this case?  The webstore can't access it right now, but it should be pretty trivial to change that.  The one bit that's missing is passing in the language separately.

[1] https://developer.chrome.com/extensions/management#method-getPermissionWarningsByManifest

Comment 2 by konsto@chromium.org, Aug 28 

I would like to actually send only the permissions list. Manifest files could be really big and we try to reduce the network usage as much as possible.

Comment 3 by rdevlin....@chromium.org, Aug 28 

The permissions for an extension aren't all contained within the "permissions" entry in the manifest, e.g. the content scripts entry.  Theoretically, we could only send the entries that could generate permission warnings, but I'd be curious how much this actually saves us.

What causes manifest files to be so large?  Most of the larger entries, I thought, were actually permissions-related (e.g., specifying long lists of host permissions)?

Comment 4 by lottie@chromium.org, Aug 29 

Some special manifest may be very big, e.g. when the item type is SITELIST, or SHARED_MODULE. 

Also, we can't control how big a manifest file is. It's up to the developers.

Comment 5 by jawag@chromium.org, Aug 29 

Neither SITELIST or SHARED_MODULE content types are displayed in the CWS, so it seems like CWS could just not call management.getPermissionWarningsByManifest() for those types.

What's the biggest manifest file size if we exclude SITELIST and SHARED_MODULE?
►

Sign in to add a comment