Google chrome extension 为什么我的manifest.json会因为广泛的主机权限而引发长时间的审查?
chrome webstore将我的扩展标记为具有“广泛主机权限”,但我无法找出manifest.json中的原因Google chrome extension 为什么我的manifest.json会因为广泛的主机权限而引发长时间的审查?,google-chrome-extension,manifest.json,Google Chrome Extension,Manifest.json,chrome webstore将我的扩展标记为具有“广泛主机权限”,但我无法找出manifest.json中的原因 { "name": "AudioEye Smart Remediation Builder", "description": "Solve any issue of accessibility without writing code. Select elements, apply changes, and fix the web.", "devtools_
{
"name": "AudioEye Smart Remediation Builder",
"description": "Solve any issue of accessibility without writing code. Select elements, apply changes, and fix the web.",
"devtools_page": "src/main.html",
"version": "1.31.0",
"content_security_policy": "script-src 'self' https://myother.website.com/scripts/loader.js https://myotherother.website.com/somescript.js; object-src 'self'",
"author": "AudioEye",
"background": {
"scripts": [
"src/background.bundle.js"
]
},
"browser_action": {
"default_icon": {
"16": "icons/ae16.png",
"48": "icons/ae48.png",
"128": "icons/ae128.png"
},
"default_popup": "src/popup.html"
},
"content_scripts": [
{
"matches": [
"*://my.website.com/*"
],
"run_at": "document_end",
"all_frames": true,
"js": [
"src/installDefinition.js"
]
}
],
"externally_connectable": {
"matches": [
"*://my.website.com/*"
]
},
"icons": {
"16": "icons/ae16.png",
"48": "icons/ae48.png",
"128": "icons/ae128.png"
},
"manifest_version": 2,
"optional_permissions": [
"http://*/*",
"https://*/*",
"tabs"
],
"permissions": [
"cookies",
"webNavigation",
"activeTab",
"storage",
"contextMenus"
],
"web_accessible_resources": [
"src/inspected-window.bundle.js",
"src/smart-remediation-metadata.js"
]
}
我只在可选的_permissions对象中使用了广泛匹配,这使用户能够明确地允许/拒绝他们访问的每个页面上的权限
由于主机权限广泛,为什么我的扩展需要两周的审查?问题是,chrome的web store审查过程完全是一个笑话,而且大多数审查人员都不是程序员,所以我也会这样做:每次他们做对了,都会惊喜不已。不过,严肃地说,在代码方面您无能为力,因为manifest.json很好。如果你没有犯错误,比如在真正的json.oth中用
*
替换.com
,我看到你的CSP允许外部脚本,这在网上商店是不允许的——要么很快就会被完全禁止,要么可能已经被禁止了。