On Nov 20, 8:38 pm, Boris Zbarsky <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > These have been sufficient in the past to allow cross-domain reads > > during development prior to plugin development. UniversalBrowserWrite > > was actually only a convenience for processing some style information > > and is actually not critical. > > Sure. I'm just saying that depending on exactly how you're doing your > "cross-domain reads" they might no longer be sufficient. It's really > hard to say anything else given the information you're willing to provide. > > -Boris
Sorry, I must be missing something. I have been setting the .src of an IFRAME to the cross-domain URL which gives the calling javascript the HTML of the target so it can then generate the DOM structure. That is what has worked fine with the user_pref settings above. If, instead, I oculd do an XHR GET, that would be preferable. Is that the distinction you are looking for? If that is still insufficient for you, please tell me what you are looking for that makes a difference in the way the user_prefs should now be set. _______________________________________________ dev-security mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security
