Hi Julien, We're working on some APIs to make this sort of request filtering possible, but it won't happen for the initial release. In the meantime, filtering using the content script is your best, if imperfect, option.
Content scripts count as the page memory right now, since they run in the renderer. -Nick On Fri, Oct 23, 2009 at 2:26 PM, Julien Tillay <djac...@gmail.com> wrote: > hello, > In order to make an adblock+ doing the right job (and not hide some html > elements or inject style after downloading them, and render them a short > time etc), > I wonder if there is a way to really intercept the requests done after the > download of the html source code (javascript files, images or iframes > etc...) ? > > I tried to use a xhr to load the source code in background, do the right > job and then inject it in the tab but, it's ugly and doesn't works well. > (can't watch all needed events) > the goal is to avoid a large amount of useless data downloaded. you just > have to look at the javascript code for some ads and you'll know why tabs > take this huge memory. > help :s > > and an other question about the content scripts, are they part of the > memory took by the extension or are they add to the tabs affected ? > > -- > Julien TILLAY > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
