On 2/23/13 1:08 PM, matt...@salsitasoft.com wrote:
Currently I have to admit that I don't understand how the code addresses the
issue of giving content access to the responseXML DOM returned by the
Cc['@mozilla.org/xmlextras/xmlhttprequest;1'].
The DOM returned by responseXML is associated with the origin the XHR
was initialized with.
As far as how you set this origin, it used to be that you could do this
directly from a component, but now it looks like we always use the
principal of the associated window, if any.
Unfortunately, we also use that window to determine whether this is a
system XHR or not, as far as I can tell...
Clearly there is a wrapper in play but exactly what kind of wrapper and how to
penetrate it is not yet clear to me.
You really want to just give that DOM the origin of the page you want to
expose it to.
I guess the reason I'm suddenly having this problem is
https://bugzilla.mozilla.org/show_bug.cgi?id=809652
Seems pretty unlikely.
Can you pin down which nightly build the behavior change you observe
happened in? See http://harthur.github.com/mozregression/
-Boris
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
