FYI, we're going to try and give a little help to make it more obvious when you try and use extension API's that aren't available in a content script.
http://crbug.com/26128 On Thu, Oct 29, 2009 at 1:35 PM, Daniel Wagner-Hall <[email protected]>wrote: > > On 10/26/09, Bartek <[email protected]> wrote: > > Additionally, what's the proper way to test when building an > > extension? Using console.log() doesn't output anything to the console > > so it's very tough to play around with it. > > It really should. From a content script, console.log should dump it > argument to the developer console (ctrl + shift + j and press escape), > if from a background page or toolstrip, go to chrome://extensions and > click Inspect next to the relevant file... > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
