On Monday, February 25, 2013 9:45:35 AM UTC+1, mat...@salsitasoft.com wrote:
> Changing back to chrome:// URLs solves all of this (including eliminating the
> need to muck with the XHR implementation in the background page) except the
> original problem of accessing them via XHR in the sandbox. B
On Monday, February 25, 2013 4:27:24 AM UTC+1, Boris Zbarsky wrote:
> 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 al
On Monday, February 25, 2013 4:27:24 AM UTC+1, Boris Zbarsky wrote:
> > I guess the reason I'm suddenly having this problem is
> > https://bugzilla.mozilla.org/show_bug.cgi?id=809652
>
> Seems pretty unlikely.
Yes, I misanalyzed this. It appears that the root cause of the problem was that
my co
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 wi
On 2/24/13 12:44 PM, matt...@salsitasoft.com wrote:
Unfortunately I'm relying on DOMWindowCreated to inject my symbols into the
window, and this is no longer fired in FF19 with the type set to chrome.
Uh code inspection and basic testing over here suggest it fires just
fine, for what it's
On Sunday, February 24, 2013 4:27:16 AM UTC+1, Brian Smith wrote:
> I notice that your company has developed a cross-browser framework for
> building extensions. That means you are probably familiar with Chromium's
> requirements here. I believe that Chromium requires you to do things the same
>
On Friday, February 22, 2013 4:28:08 PM UTC+1, Kyle Huey wrote:
> You should look at SpecialPowersAPI.createSystemXHR. It's what we use in
> our test suite to do this.
Hi Kyle,
Thanks for this. I need to replace the XMLHttpRequest constructor with my own
constructor, so I can't call createSyste
- Original Message -
> From: "Matthew Gertner"
> To: dev-platform@lists.mozilla.org
> Sent: Friday, February 22, 2013 7:02:40 AM
> Subject: Accessing @mozilla.org/xmlextras/xmlhttprequest;1 from content
>
> I have an extension that loads an HTML file into a
On Fri, Feb 22, 2013 at 7:02 AM, Matthew Gertner wrote:
> Is there a better way to let content do crossdomain XHR? Or is there a
> good way to provide a usable XML DOM from chrome to content? I can always
> reparse responseText to create my own DOM if there's a way to create a
> content-friendly D
I have an extension that loads an HTML file into a hidden and runs
script in the context of the hidden browser window. That script needs to be
able to make crossdomain XHR requests to chrome:// and resource:// URLs that
are apparently now blocked in Firefox 19 (they weren't blocked in Firefox 1
10 matches
Mail list logo
