Ok, that makes sense. On Tue, Nov 3, 2009 at 2:07 PM, Aaron Boodman <a...@chromium.org> wrote:
> No, it should work for images (and things like text/plain). One reason > people frequently want to do this is so that they can improve the > rendering of images, eg by adding a black background or a nice border. > > Here is the bug for this in our system. Feel free to star it if you > want to track progress, though it is pretty low priority relative to > other things right now: > > http://crbug.com/12082 > > - a > > On Tue, Nov 3, 2009 at 1:01 PM, Antony Sargent <asarg...@chromium.org> > wrote: > > It's definitely inconsistent. Do you have a use case where you'd want the > > content script to run on non-html content urls? At first thought it seems > > the bug may be that we run at document_end. > > > > On Tue, Nov 3, 2009 at 10:24 AM, donaddon <don...@verizon.net> wrote: > >> > >> I have a content script that runs at document_start. > >> When I navigate to a direct image (or a PDF), my document_start > >> content script doesn't appear to be loaded (my console.log statements > >> aren't displayed). document_end scripts are loaded and are able to > >> manipulate the DOM that wraps the image. > >> > >> Bug? > >> > >> 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-extensions@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 -~----------~----~----~----~------~----~------~--~---
