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
-~----------~----~----~----~------~----~------~--~---

Reply via email to