On Sat, Oct 31, 2009 at 4:29 PM, Evan Martin <[email protected]> wrote: > > I've updated this to the browser actions API.
Thanks for trying again. > - The docs are behind the code (had to read the code once or twice to > figure out what was going wrong). Were you using trunk or dev? The docs on http://code.google.com/chrome/extensions are the ones for the dev channel, and they should be correct. Though there is some support for browser actions on dev right now, it was not complete and the API was in flux, so we purposely didn't document it. If you developed against that, you're probably going to have to change it for the next dev channel (sorry). You can always see the trunk docs, here: http://code.google.com/chrome/extensions/trunk > - Not exactly clear sometimes which error console you're supposed to > look at; the workflow of "reload, see what error happened this time" > takes a few too many clicks. Would be nice if chrome://extensions/ > remembered whether I had the developer tools turned on or off. We have a bug to keep the inspector open (http://crbug.com/25287). It is nontrivial to fix, but we're hoping to get it in for beta. As for knowing which console to look at, I agree it sucks. For now, we're going to have to just document it, but I hope to come up with some kind of "master console output" later. - a --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
