On Tue, Sep 1, 2009 at 11:16 PM, Matias Pelenur<[email protected]> wrote: > > Yeah, I agree, and I see the errors/logs. But it would be great if we > could also put breakpoints on the content script(s), the way you can > do it for a background page or toolstrip. Probably a TODO(chromium- > team) (or implement it myself, I guess :)
I've often thought this would be handy. Before the content script was properly sandboxed from the page context, you could simply make relevant calls from the developer console, but sandboxing separated them out. I imagine there will be security issues with allowing decent debugging (unless it was perhaps behind a --extensions-development flag?) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
