On Sun, Dec 13, 2009 at 10:36 PM, Adam Barth <aba...@chromium.org> wrote: > On Sun, Dec 13, 2009 at 8:04 PM, Ilya Sukhar <ilya.suk...@gmail.com> wrote: >> It looks like view-source pages no longer get content scripts. Adam, is that >> intentional and the behavior to expect going forward? > > I wasn't aware of any change, but Aaron might know more. It seems > like we should allow content scripts in view-source if you ask for > view-source in the manifest. > > In general, the view-source implementation is really wonky because > sometimes we present it with "view-source:" in the URL and sometimes > we represent it with a flag on the Frame object.
This wasn't changed purposefully. OTOH, should http://*/* match view-source:// ? That seems a bit unexpected. Maybe match patterns should explicitly support the view-source:// pseudo protocol. - a -- 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.
