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 :)
-matias On Sep 1, 6:02 pm, "Mike H." <[email protected]> wrote: > the errors will show up in teh actual page's logs... so if your content > script runs on google.com, go to google.com and open the console (ctrl + > shift + j) and all console.log()s and errors from the content script will be > there > > On Tue, Sep 1, 2009 at 3:50 PM, Matias Pelenur <[email protected]>wrote: > > > > > > > I have no problem opening the developer tools window for a toolstrip, > > or for a background page (by clicking on Inspect from the > > chrome://extensions/ > > page). But how can I debug (add breakpoints, etc) a content script? It > > doesn't appear on the Scripts list for the page it's injected into (I > > assume that's because of isolation). Is there any way to access it > > through the developer tools? > > > Thanks, > > matias --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
