Message from discussion
Accessing iframe content with a Chrome extension - not via content script
Received: by 10.68.234.38 with SMTP id ub6mr121337pbc.2.1336501144262;
Tue, 08 May 2012 11:19:04 -0700 (PDT)
X-BeenThere: chromium-extensi...@chromium.org
Received: by 10.68.242.40 with SMTP id wn8ls195712pbc.1.gmail; Tue, 08 May
2012 11:18:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.216.42 with SMTP id on10mr19213pbc.3.1336501134617; Tue, 08
May 2012 11:18:54 -0700 (PDT)
Authentication-Results: ls.google.com; spf=pass (google.com: domain of
devinrho...@gmail.com designates internal as permitted sender)
smtp.mail=devinrho...@gmail.com; dkim=pass
header...@gmail.com
Received: by to5g2000pbc.googlegroups.com with HTTP; Tue, 8 May 2012 11:18:54
-0700 (PDT)
Date: Tue, 8 May 2012 11:18:54 -0700 (PDT)
In-Reply-To: <5d50b85b-fbcc-4c65-8efa-8d5cd361974c@k24g2000yqe.googlegroups.com>
References: <5d50b85b-fbcc-4c65-8efa-8d5cd361974c@k24g2000yqe.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3)
AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.41 Safari/536.5,gzip(gfe)
Message-ID: <2e84f379-f823-4f59-a5fd-010673a690d8@to5g2000pbc.googlegroups.com>
Subject: Re: Accessing iframe content with a Chrome extension - not via
content script
From: Devin <devinrho...@gmail.com>
To: Chromium-extensions <chromium-extensi...@chromium.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
You can inject a content script to all_frames and into the iframe, but
you can only access the inside of an iframe if it's the same origin.
you can also more directly use postMessage for frame messaging,
instead of background page messaging
On Apr 5, 5:30=A0am, UVL <andrea.do...@gmail.com> wrote:
> I need tho access the contents of an iframe via javascript.
>
> I know this is usually blocked due to cross origin policies, but I
> need this inside a Chrome extension, and usually in these cases the
> manifest directives can unlock security policies.
>
> I've found a lot of request about content scripts accessing iframes,
> but in my case it is not a content script, it is just an iframe inside
> a extension/app page.
>