Question

Well, a often discussed thing. But I can’t get it work. What has to be done:

• The Content or Background Script has to communicate with the iframe et vice versa.
• The iframe is under my hand, so there is everything possible.

I tried a lot. It doesn’t work at all. For instance: If I deploy the content script on every page with allFrames=true via (manifest). Ok, makes sense. The iframe is created later so the trigger won’t be called. So let’s do this: create the iframe and afterwards sending an executeScript request:

 chrome.tabs.executeScript(tabinst.tab_id, { allFrames: true, file:'frame.js'}, function() {
      console.log("done");
 });

But that doesn’t work either. Has anyone a solution to communicate with an XDM iframe and a chrome extension?

PS: How nice it would be if the chrome extension would allow postMessage on iframe

EDIT1:

The code doesn’t get injected in the iframe. Scenario:

The file “file.js” has a simple foo function in it. I now apply it with the above statement 2 seconds after the iframe was created and showed. This function foo is not available in the iframe…but is in the content script. The ReferenceError is thrown by trying to execute foo within the iframe (by click).

So, it’s not a timing thing. And it doesn’t matter if I apply the Scripts via manifest and all_frames true. If that would work, the content_script would be available. But is not.

EDIT2:
@serg

Yeah, thanks, that works! I just got through it. My problem was, that I assumed that when the callback of chrome.tabs.executeScript is called, the requested script is ended and the including DOM manipulation finished. But that’s actually not the case. It takes some time till the script in the iframe and the containing listener is ready.

So I had to send a chrome.extension.sendRequest from that script in the iframe and then start some code out of the background listener to manipulate the iframe. Thanks for your help.

PS: It’s also possible to do it without “all_frames”: true. It just takes some time till the dynamic iframe is ready. With a timeout it works. For the most cases, this is not useful, but maybe someone has another user interaction first.

PPS: I still can’t see why it’s possible like this, and not possible to send postMessage events. But maybe somewhen this will works.

Answer 1

I just tested and content script is getting injected into dynamically created iframes (I used manifest). I think the problem is you are trying to access content script’s function within iframe, which is not allowed.

Inside your iframe you can’t just do:

<a onclick="contentScriptFunction()"></a>

You need to be adding event listener from within the content script:

$("a").click(contentScriptFunction);