Thanks, can one of you create a bug with as much information as you
have? I'll try and duplicate asap.
Collin, are you seeing this on trunk or dev?
- a
On Mon, Dec 7, 2009 at 1:53 PM, Collin Jackson <jack...@chromium.org> wrote:
> I'm having trouble getting content scripts to run in background page
> iframes on Windows as well. I'm not sure if it's related to the issue
> that Don is describing, or if it's a separate issue. It was working
> fine as recently as a few days ago.
>
> Here's a simple test case that tries to load a www.google.com iframe
> in the background page. The content script should run and print a
> message to the background page's inspector console, but it doesn't. It
> does seem to run the content script when iframes are encountered on
> ordinary web pages, however. I tested it on Google Chrome 4.0.249.25.
>
> manifest.json:
>
> {
> "background_page": "background.html",
> "content_scripts": [ {
> "all_frames": true,
> "js": [ "demo.js" ],
> "matches": [ "http://*/*";, "https://*/*"; ],
> "run_at": "document_end"
> } ],
> "description": "Test case for content scripts in iframes.",
> "name": "Reduced Test Case",
> "permissions": [ "tabs", "http://*/*";, "https://*/*"; ],
> "version": "1.0"
> }
>
> background.html:
>
> <html>
> <body>
> <iframe src='http://www.google.com/'></iframe>
> </body>
> </html>
>
> demo.js:
>
> console.log("Content script ran in " + document.location);
> document.body.className = 'content script ran';
>
> On Mon, Dec 7, 2009 at 12:14 PM, donaddon <don...@verizon.net> wrote:
>> What I'm seeing with current Chromium builds (not dev channel) for Mac
>> (and I suspect Linux) is that content scripts only seem to be injected
>> in iframes if they are matched by the parent and all_frames is true.
>>
>> Let me clarify: Previously (and on Windows of Chromium), if I have a
>> child iframe that has a URL that matches a content script, then that
>> content script would be loaded regardless of whether the parent
>> matched or what was set for all_frames in the parent.
>>
>> Is this intentional, or a known problem with the Mac (and I believe
>> Linux) builds?
>>
>> Thanks!
>>
>> --
>>
>> You received this message because you are subscribed to the Google Groups
>> "Chromium-extensions" group.
>> To post to this group, send email to chromium-extensi...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> chromium-extensions+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/chromium-extensions?hl=en.
>>
>>
>>
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Chromium-extensions" group.
> To post to this group, send email to chromium-extensi...@googlegroups.com.
> To unsubscribe from this group, send email to
> chromium-extensions+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/chromium-extensions?hl=en.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Chromium-extensions" group.
To post to this group, send email to chromium-extensi...@googlegroups.com.
To unsubscribe from this group, send email to
chromium-extensions+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/chromium-extensions?hl=en.
