如何修复 chrome-extension 内联 JavaScript 调用错误？

我正在制作一个 chrome 扩展，但是当我尝试启动 onclick() 事件时，我似乎收到以下错误。

Refused to load the script 'https://apis.google.com/js/client.js?onload=handleClientLoad' because it violates the following Content Security Policy directive: "script-src 'self' blob: filesystem: chrome-extension-resource:"

and

Refused to execute inline event handler because it violates the following Content Security Policy directive: "script-src 'self' blob: filesystem: chrome-extension-resource:". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution.

这是我的manifest.json：

{
  "manifest_version": 2,

  "name": "SECURE",
  "description": "this extension offers secure communication for GMAIL     users",
  "version": "1.0",

 "browser_action": {
 "default_icon": "resources/icon16.png",
 "default_popup": "popup.html",
 "default_title": "Click here!"


 },

 "background":{
   "scripts":["background.js"]
},

 "content_scripts": [
  {
   "matches": ["http://*/*", "https://*/*"],
   "js":["myscript.js"],
   "run_at": "document_end"
  }
  ],
"permissions": ["identity", "https://accounts.google.com/*",  "https://www.googleapis.com/*"],

"oauth2": {
   "client_id": "975410329966.apps.googleusercontent.com",
 "scopes": [
   "<all urls>",
   "https://www.googleapis.com/auth/drive",
   "https://mail.google.com/",
   "https://www.googleapis.com/auth/gmail.login",
   "https://www.googleapis.com/auth/gmail.compose",
   "https://www.googleapis.com/auth/gmail.readonly",
   "https://www.googleapis.com/auth/gmail.send"
  ],

 "content_security_policy":"script-src 'self'  'unsafe-inline' 'unsafe eval'  https://apis.google.com/js/client.js?; object-src 'self'"


}
}

任何有助于修复此错误的帮助将不胜感激。

默认情况下内容安全政策 https://developer.chrome.com/extensions/contentSecurityPolicy，内联脚本不会被加载，只能加载本地脚本。您可以通过以下方式放宽默认策略：

1. 内联脚本。看一眼官方指南 https://developer.chrome.com/extensions/contentSecurityPolicy#relaxing-inline-script，可以通过在策略中指定源代码的 Base64 编码哈希来将内联脚本列入白名单。看元素的哈希用法 https://www.w3.org/TR/2015/CR-CSP2-20150721/#script-src-hash-usage举个例子。

   但我相信更好的方法是将这个逻辑提取到一个单独的脚本中，而不是使用内联脚本。

2. 远程脚本。您可以将脚本资源列入白名单https://apis.google.com/js/client.js?onload=handleClientLoad通过以下部分manifest.json

   "content_security_policy":"script-src 'self' https://apis.google.com; object-src 'self'"
   

   另外，我相信更好的方法可能是下载远程client.js并将其作为本地脚本包含在内。

请注意，根据描述内联脚本 https://developer.chrome.com/extensions/contentSecurityPolicy#relaxing-inline-script, unsafe-inline不再有效。

在 Chrome 45 之前，还没有任何机制可以放松对执行内联 JavaScript 的限制。特别是，获取包含“unsafe-inline”的脚本策略将无效.