On Fri, Aug 21, 2009 at 4:50 PM, Colin Bleckner<[email protected]> wrote: > > I'll state up front that this is a slightly odd feature request. :) But > I think it could be pretty useful in the long run. > > I've been using console.log pretty heavily and I'd like to keep using > it. Unfortunately, if something goes wrong on a user's machine it's > difficult to walk the user through all the steps needed to find the log > output. Is the console output stored in an internal Chrome web page or > something that I can drive the user to instead? I'd love to have a link > in my settings dialog that says "View log file" and clicking it opens up > a page containing console's output for my background.html's view.
WebInspector keeps some number of the last console.log entries in memory in case you want to bring up the inspector on a page and see the old errors. We could add a link to chrome://extensions which would popup the inspector for the appropriate page with the console open. Is that enough? (yes, I know that chrome://extensions isn't that easy to find either, that's on the TODO list as well) Or do you really want an API to get access to the contents of these errors? In either case, please file a feature request in the issue tracker. Erik > > Otherwise I'm going to have to create some sort of log system myself and > I'd really rather not do that. :) > > Cheers, > Colin > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
