Skip to content

Conversation

@anaran
Copy link
Contributor

@anaran anaran commented Dec 13, 2013

Fix links

@anaran
Copy link
Contributor Author

anaran commented Dec 13, 2013

I would like to do the same for firefox.

Main motivation was that consoleHistory is very limited for Chrome (30) and console log messages would be useful to retain as well for review upon the next debug session.

Also when chrome crashes (not so infrequent for canary builds) then it is too late to save to console log messages manually.

See also http://stackoverflow.com/questions/20524595/how-to-access-firefox-web-console-command-history where I got some help for firefox.

But my focus have shifted from the mere console commands to the full console log.

@addyosmani
Copy link

👍

@anaran
Copy link
Contributor Author

anaran commented Dec 15, 2013

Thanks Addy!

@anaran
Copy link
Contributor Author

anaran commented Dec 16, 2013

Let's put that one on hold unless you have spent effort on it yet.

I plan some generalization for chrome and firefox.

It also works pretty well in webchat tabs for instance.

Add consoleAutosave snippet (for Google Chrome)

Fix links

Cherry-pick lost content from previous commit of consoleAutosave/README.md

typo fix

Unified functionality with autosaveElement.js.
autosaveElement.js is already useful in firefox and chrome
to select element (or ancestor) based on selection in tabs like webchat.
TODO: autosave webconsole in firefox.

That's readable after [Format JS] in eclipse orion editor.
Also passes JSLint.

Normalize single-line comments, with documented eclipse orion replace command.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants