browser.tabs.sendMessage（）：错误：接收结束不存在

Question

我试图运行tabs.sendMessage() MDN page上给出的示例代码。所以我的代码是：

manifest.json的：

{ 
    "manifest_version": 2, 
    "name": "test1", 
    "version": "1.0", 
    "description": "test", 
    "icons": { 
     "48": "icons/Ruler48.png" 
    }, 
    "permissions": [ 
     "notifications", 
     "tabs", 
     "activeTab" 
    ], 
    "browser_action": { 
     "default_icon": "icons/Ruler48.png", 
     "default_title": "test" 
    }, 
    "content_scripts": [{ 
     "matches": ["*://*/"], 
     "js": ["content-script.js"] 
    }], 
    "background": { 
     "scripts": ["bgS.js"] 
    } 
} 

bgS.js：

function onError(error) { 
    console.error(`Error: ${error}`); 
} 

function sendMessageToTabs(tabs) { 
    for (let tab of tabs) { 
    console.log(tab.id); 
    browser.tabs.sendMessage(
     tab.id, 
     {greeting: "Hi from background script"} 
    ).then(response => { 
     console.log("Message from the content script:"); 
     console.log(response.response); 
    }).catch(onError); 
    } 
} 

browser.browserAction.onClicked.addListener(() => { 
    browser.tabs.query({ 
    currentWindow: true, 
    active: true 
    }).then(sendMessageToTabs).catch(onError); 
}); 

内容的script.js：

browser.runtime.onMessage.addListener(request => { 
    console.log("Message from the background script:"); 
    console.log(request.greeting); 
    return Promise.resolve({response: "Hi from content script"}); 
}); 

我与网络的内线运行运行它，点击浏览器的操作按钮，在控制台后，我得到这个消息：Error: Error: Could not establish connection. Receiving end does not exist.

输出从web-ext run --verbose

web-ext run --verbose 
[program.js][debug] Getting the version from package.json 
[program.js][info] Version: 1.8.0 
[program.js][debug] Getting the version from package.json 
[cmd/run.js][info] Running web extension from C:\test 
[util/manifest.js][debug] Validating manifest at C:\test\manifest.json 
[cmd/run.js][debug] Creating new Firefox profile 
[cmd/run.js][debug] Deferring extension installation until after connecting to the remote debugger  
[firefox/index.js][debug] Checking if remote Firefox port 6005 is available 
[firefox/remote.js][debug] Connecting to Firefox on port 6005 
[firefox/index.js][debug] Executing Firefox binary: C:\Program Files\Mozilla Firefox\firefox.exe  
[firefox/index.js][info] Use --verbose or open Tools > Web Developer > Browser Console to see logging 
[cmd/run.js][debug] Connecting to the remote Firefox debugger 
[firefox/remote.js][debug] Connecting to Firefox on port 6005 
[cmd/run.js][debug] Retrying Firefox (0); connection error: Error: connect ECONNREFUSED 127.0.0.1:6005 
[firefox/remote.js][debug] Connecting to Firefox on port 6005 
[cmd/run.js][debug] Retrying Firefox (1); connection error: Error: connect ECONNREFUSED 127.0.0.1:6005 
[firefox/remote.js][debug] Connecting to Firefox on port 6005 
[cmd/run.js][debug] Retrying Firefox (2); connection error: Error: connect ECONNREFUSED 127.0.0.1:6005 
[firefox/remote.js][debug] Connecting to Firefox on port 6005 
[firefox/index.js][debug] Firefox stdout: Started debugger server on 6005 
[cmd/run.js][debug] Retrying Firefox (3); connection error: Error: connect ECONNREFUSED 127.0.0.1:6005 
[firefox/remote.js][debug] Connecting to Firefox on port 6005 
[firefox/remote.js][debug] Connected to the remote Firefox debugger 
[firefox/index.js][debug] Firefox stderr: JavaScript strict warning: resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/security/socket.js, line 778: ReferenceError: reference to undefined property this._handshakeTimeout 
[firefox/index.js][debug] Firefox stderr: JavaScript strict warning: chrome://browser/content/browser.js, line 6573: SyntaxError: applying the 'delete' operator to an unqualified name is deprecated 
[firefox/remote.js][debug] installTemporaryAddon: {"addon":{"id":"d71da5f6ee8174302deb5edfa887679913cd71ed@temporary-addon","actor":false},"from":"server1.conn0.addonsActor3"} 
[firefox/remote.js][info] Installed C:\test as a temporary add-on 
[cmd/run.js][info] The extension will reload if any source file changes 
[util/file-filter.js][debug] Resolved path **/*.xpi with sourceDir C:\test to C:\test\**\*.xpi 
[util/file-filter.js][debug] Resolved path **/*.zip with sourceDir C:\test to C:\test\**\*.zip 
[util/file-filter.js][debug] Resolved path **/.* with sourceDir C:\test to C:\test\**\.* 
[util/file-filter.js][debug] Resolved path **/.*/**/* with sourceDir C:\test to C:\test\**\.*\**\* 
[util/file-filter.js][debug] Resolved path **/node_modules with sourceDir C:\test to C:\test\**\node_modules 
[util/file-filter.js][debug] Resolved path **/node_modules/**/* with sourceDir C:\test to C:\test\**\node_modules\**\* 
[util/file-filter.js][debug] Resolved path C:\test\web-ext-artifacts with sourceDir C:\test to C:\test\web-ext-artifacts 
[util/file-filter.js][debug] Resolved path C:\test\web-ext-artifacts\**\* with sourceDir C:\test to C:\test\web-ext-artifacts\**\* 
[watcher.js][debug] Watching for file changes in C:\test 
[firefox/index.js][debug] Firefox stderr: JavaScript strict warning: chrome://browser/content/tabbrowser.xml, line 640: ReferenceError: reference to undefined property this.mBrowser.initialPageLoadedFromURLBar 
[firefox/index.js][debug] Firefox stdout: 1486682957594 addons.webextension.d71da5f6ee8174302deb5edfa887679913cd71ed@temporary-addon WARN Please specify whether you want browser_style or not in your browser_action options. 
[firefox/index.js][debug] Firefox stderr: JavaScript strict warning: chrome://global/content/bindings/browser.xml, line 385: ReferenceError: reference to undefined property tabBrowser.localName 
[firefox/index.js][debug] Firefox stderr: JavaScript strict warning: resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/node-properties/node-properties.js, line 134: ReferenceError: reference to undefined property control.resume 
[firefox/index.js][debug] Firefox stderr: JavaScript strict warning: resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/node-properties/node-properties.js, line 124: ReferenceError: reference to undefined property options._comments[c] 
[firefox/index.js][debug] Firefox stderr: JavaScript strict warning: resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/node-properties/node-properties.js, line 130: ReferenceError: reference to undefined property options._separators[c] 
[firefox/index.js][debug] Firefox stderr: JavaScript strict warning: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/unload.js, line 31: ReferenceError: reference to undefined property observers[i].value 
[firefox/index.js][debug] Firefox stderr: JavaScript strict warning: resource://gre/modules/ProfileAge.jsm, line 202: ReferenceError: reference to undefined property times.reset 
[firefox/index.js][debug] Firefox stderr: JavaScript strict warning: resource://gre/modules/LoginStore.jsm, line 275: ReferenceError: reference to undefined property this.data.version 
[firefox/index.js][debug] Firefox stderr: JavaScript strict warning: chrome://global/content/bindings/browser.xml, line 385: ReferenceError: reference to undefined property tabBrowser.localName 

这，什么浏览器控制台中，第一条消息出现在我安装它之前。我的意思是它在安装之前就已经存在了，所以它会默默安装。点击按钮后，我得到了最后的两个消息，第一个从该行给出tab.idconsole.log(tab.id)然后错误：

1486683758937 addons.webextension.16f1634b55daa52a653f3a2ba33358a691bb015a@temporary-addon WARN Please specify whether you want browser_style or not in your browser_action options. 
10 bgS.js:8:3 
Error: Error: Could not establish connection. Receiving end does not exist. bgS.js:3:3 

Answer 1

您所看到的结果时，有一个内容脚本为您的扩展定义没有runtime.onMessage监听器错误在tabs.sendMessage()的调用中指定的选项卡中。这可能是因为没有内容脚本，或者因为已注入的内容脚本没有为runtime.onMessage添加侦听器。

您应该记住，您不能将内容脚本插入到具有像about:newtab，about:debugging等网址的页面中。另外，Firefox不允许您将脚本注入addons.mozilla.org的页面。

由于您的可能并非您所期望的，因此您的问题已复杂化。你可能是为了你的matches是：

"matches": ["*://*/*"], 

注意在匹配模式结束后*。您目前使用的模式"*://*/"只会匹配使用http或https方案加载的任何域上的首页。例如，它不会匹配https://www.google.com/?gws_rd=ssl，但会匹配http://www.example.com/。

鉴于您的代码直接在用户点击浏览器或页面操作按钮时执行，您需要以某种合理的方式处理此错误，以便向用户提供他们所要求的无法完成的反馈，因为用户将点击页面上的按钮，如about:newtab，其中将导致此错误。你如何处理这个错误，将取决于你的代码在做什么。与其设置一种情况，用户点击他们希望工作的启用按钮，更好的选择是在不能执行代码的页面上禁用您的操作按钮（对于浏览器操作，使用browserAction.disable()）。