I\'m writing a chrome extension and I\'m struggling to pass an object back from the main page to the context script. I can\'t seem to access the window\'s variables.
The global variables of a content script and a page-level injected script are isolated.
Content scripts execute in a special environment called an isolated world. They have access to the DOM of the page they are injected into, but not to any JavaScript variables or functions created by the page. It looks to each content script as if there is no other JavaScript executing on the page it is running on. The same is true in reverse: JavaScript running on the page cannot call any functions or access any variables defined by content scripts.
Emphasis mine.
To pass the data to your content script, you don't have to employ extra DOM elements. You just need custom DOM events.
// Content script
// Listen for the event
window.addEventListener("FromPage", function(evt) {
/* message is in evt.detail */
}, false);
// Page context
var message = {/* whatever */};
var event = new CustomEvent("FromPage", {detail: message});
window.dispatchEvent(event);
See this answer for far more details.
Above answer may work but I don't think it is the correct way ...
First:
If you already published your extension, get the application key and put it into your manifest "key" as described here:
copy the "key" atring from the console into your local manifest.json:
"key": "MIIBIjANBgkqhkiG9w...RwIDAQAB",
This will ensure your local and published extension have the same extensionId
Second:
chrome://extensions
and looking for ID under your extension titleThird:
in your background script (ie background.js) listen for msgs like this:
chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
if (message.name === 'msg1') {
alert(message.key1);
}
});
in your content script (ie contentScript.js) send msgs like this:
chrome.runtime.sendMessage(extensionId, { name: 'msg1', key1: 'value1'}, undefined, (response) => {});
(replace extensionId with the one you got in the second step)