Many thanks, Roman, but I keep getting the following error when using your workaround:
Uncaught TypeError: Object [object Object] has no method 'stringify' chrome://devtools/chrome/RendererExtensionBindings Any idea where it comes from and how to fix it? Cheers, Yata On Sep 24, 7:16 am, Roman N <[email protected]> wrote: > I just wrote a workaround for cross domain XHR's not working in > content scripts: > > http://gist.github.com/192538 > > Hope that helps!Roman > > On Sep 17, 7:49 pm, Aaron Boodman <[email protected]> wrote: > > > It is working by design, but I agree that it is a bit surprising. That is > > something others have brought up. > > - a > > > On Thu, Sep 17, 2009 at 7:05 PM, Jon Stritar <[email protected]> wrote: > > > > While messing around with cross-domain XHR in content scripts, I > > > noticed that the match patterns ignore ports. For example, if I wanted > > > to insert a content script onhttp://localhost:8000/test/, I currently > > > need to specify "http://localhost/test/"; without the port. I'm not > > > sure if this is a matches or documentation bug. > > > > --Jon > > > > On Sep 17, 9:41 pm, Nick Baum <[email protected]> wrote: > > > > Actually, you now have to go use /trunk/ to see the latest version of > > > > the > > > > docs:http://code.google.com/chrome/extensions/trunk/content_scripts.html > > > > > I just switched the default to /dev/ since that's the most stable > > > > version > > > > available. > > > > > -Nick > > > > > On Thu, Sep 17, 2009 at 6:18 PM, Aaron Boodman <[email protected]> > > > wrote: > > > > > Although, now that I look again, I think we should probably add > > > > > another > > > > > bullet point to explicitly call out the cross-origin XHR limitation. I > > > will > > > > > do that. > > > > > - a > > > > > > On Thu, Sep 17, 2009 at 6:17 PM, Aaron Boodman <[email protected]> > > > wrote: > > > > > >> Good news: We just updated that part of the docs today :) > > > > >>http://code.google.com/chrome/extensions/content_scripts.html > > > > > >> <http://code.google.com/chrome/extensions/content_scripts.html>- a > > > > > >> On Thu, Sep 17, 2009 at 6:08 PM, Jon Stritar <[email protected]> > > > wrote: > > > > > >>> Cross origin requests aren't working for me in content scripts > > > either, > > > > >>> even with the correct permissions. It would be helpful if this > > > > >>> limitation was documented, otherwise its easy to spin for a while > > > > >>> thinking our manifest.json files are incorrect. > > > > > >>> --Jon > > > > > >>> On Sep 10, 2:10 pm, Aaron Boodman <[email protected]> wrote: > > > > >>> > On Thu, Sep 10, 2009 at 11:01 AM, uprise78<[email protected]> > > > wrote: > > > > >>> > > They work from background pages for me but not from content > > > scripts. > > > > >>> > > I was under the impression that with the proper permissions they > > > > >>> would > > > > >>> > > work from content scripts as well but I guess that is not that > > > case. > > > > > >>> > No, not yet. Though that is something I would like to pursue > > > someday. > > > > > >>> > - a --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
