Home/ Questions/Q 3316570
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T22:29:06+00:00

I’ve got a little problem with UserScripts in Google Chrome, to be precise with

  • 0

I’ve got a little problem with UserScripts in Google Chrome, to be precise with getting to the object window of an iframe. Very doable via the Google Chrome console, very impossible via the UserScript or so it seems so far. To be honest it seems as if it was on purpose, as if there was some reason why I’m not allowed to access other window objects.

document.body.innerHTML += "<iframe name='iframe'></iframe>";
console.log(top.frames.iframe);
console.log(window.frames.iframe);
console.log(unsafeWindow.frames.iframe);
console.log(document.getElementsByName('iframe')[0].contentWindow);
console.log(document.getElementsByName('iframe')[0].contentDocument.defaultView);

–>

chrome-extension://eelclpmekkanegjojjmaldeddncficoj/script.js:14 undefined
chrome-extension://eelclpmekkanegjojjmaldeddncficoj/script.js:15 undefined
chrome-extension://eelclpmekkanegjojjmaldeddncficoj/script.js:16 undefined
chrome-extension://eelclpmekkanegjojjmaldeddncficoj/script.js:17 undefined
chrome-extension://eelclpmekkanegjojjmaldeddncficoj/script.js:18 undefined

Might I ask what Chrome’s problem is? I don’t really get why should a UserScript have lesser access to javascript than a normal script, what are the implications? By the way, yes, the iframe is on the same domain and protocol. 🙁

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    UnsafeWindow isn’t support by Chrome, try TamperMonkey, pretty sure it provides read-only access to that variable.

    contentWindow.document isn’t available for Chrome. contentDocument should work.

    Also, XMLHttpRequest for cross domains also aren’t supported. Most of these are for security purposes. Userscripts in Chrome are content scripts, they cannot access the functions/variables defined by web pages or by other content scripts. It’s mostly for security and isolation of scripts, to prevent scripts from conflicting with each other.

    As for document.getElementsByName(‘iframe’)[0].contentWindow, I think it’s because the way you’re trying to add in your iframe. For starters, don’t name your iframe as ‘iframe’, always a very bad practice.

    Instead to attempting to add it into the body’s innerHTML, use appendChild(), and append a new iframe object into document.body. Also, instead of document.getElementsByName, try document.body.getElementsByName.

    I write greasemonkey scripts for firefox, and Chrome seems too restrictive. And I hope you know about the location hack for userscripts. Check out http://wiki.greasespot.net/Location_hack . You can use Javascript in your userscripts 😉 And just to let you know right now, I would VERY much warn against messing with iframes and userscripts. I’ve wrote a script for Greasemonkey, been trying for 6 months, but somehow, when I involve code inside the iframe, half of the time, that result is undefined, and I never get into that problem with javascript. Also, if you inject .js script objects into a document from a userscripts, the new code is still somehow affected, and so how, randomly, elements show up as undefined. After 6 months of trying, I gave up, and I just have a bookmarklet just injects a .js script into documents manually. Of course, you don’t have to do that, you can just use a location hack to inject the code from a userscript. But as for writing entire scripts based on userscripts for iframes, I’m staying far far away…

    • 0