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 <[email protected]> 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 [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 -~----------~----~----~----~------~----~------~--~---
