No such interface supported
Enlightening, no? The error message is spread like a rash over online fora, so it was difficult to see exactly which problem I was having. However, it generally relates to weird DOM manipulations, often involving different parent frames or windows. So as I was scripting between browser windows, I soon realized from this post that iI was inconsistent in my use of document objects as the factory for new nodes in the other window.
If you’re working on a particular document, and that document happens to be in another window, then IE will only let you add nodes to that document if they’ve been created by that document:
var div = window.opener.document.getElementById(”foo”);
// Works in IE and Firefox
// Fails in IE
I don’t honestly know if Firefox could be tempting security problems here, or even if the security all gets fixed behind the scenes (Firefox changing the node ownership). All I have to go off is IE’s robotic, confusing warnings, like Robbie The Robot after some internal electronic catastrophe, and Firefox’s mute, and possibly dangerous, consent.