41–46 of 46 posts
There are a lot pronouns used in this article referring to a "permission". What permission are they referring to? I pushed out an update to a Chrome extension a few days ago and it was live in a matter of hours. Is there some specific permission that triggers this review?
There are a lot pronouns used in this article referring to a "permission". What permission are they referring to? I pushed out an update to a Chrome extension a few days ago and it was live in a matter of hours. Is there some specific permission that triggers this review?
From a comment three days ago: > Right now I'm asking for "all permissions" for our extension as I need to inject a header in an HTTP response for CORS. So we're under auditing for every update.
There are a lot pronouns used in this article referring to a "permission". What permission are they referring to? I pushed out an update to a Chrome extension a few days ago and it was live in a matter of hours. Is there some specific permission that triggers this review?
"permissions": [
"activeTab",
"fileBrowserHandler",
"webRequest",
"webRequestBlocking",
"webNavigation",
"",
"storage",
"tabs",
"tabCapture",
"cookies",
"http://localhost:8500/rest/v1/capture/trigger",
"contextMenus",
"unlimitedStorage",
"declarativeContent",
"idle",
"storage"
],
Earlier quoted context omitted.
Improve your QA process and you will not be waylaid by something as simple as a typo.
Hopefully there'd be an option to roll back to some previously approved/released version. So your users may have to wait longer for the exciting new functionality, but at least they won't be screwed.
There are a lot pronouns used in this article referring to a "permission". What permission are they referring to? I pushed out an update to a Chrome extension a few days ago and it was live in a matter of hours. Is there some specific permission that triggers this review?
They seem to be asking for: "permissions": [ "activeTab", "fileBrowserHandler", "webRequest", "webRequestBlocking", "webNavigation", " ", "storage", "tabs", "tabCapture", "cookies", "http://localhost:8500/rest/v1/capture/trigger", "contextMenus", "unlimitedStorage", "declarativeContent", "idle", "storage" ], I think is the scary one that lets it read and change all data on any website you visit.
I really hope this gets changed as this currently makes fixing small changes a massive, and wanting to release a feature at the same time on a website and extension means the chrome version must be done a week in advance. This is really killing productivity