Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is that possible for consoleexport be a standalone plugin ? #6

Open
EvanHon opened this issue Oct 8, 2013 · 2 comments
Open

Is that possible for consoleexport be a standalone plugin ? #6

EvanHon opened this issue Oct 8, 2013 · 2 comments

Comments

@EvanHon
Copy link

EvanHon commented Oct 8, 2013

Firebug is too heavy, it will cause memory leak itself, is that possible for consoleexport not rely on firebug but can still log the console export into the local file? If this cames true, that's really what I want.

@EvanHon
Copy link
Author

EvanHon commented Oct 8, 2013

I think if we need this came true, we need to deep dive to see how firebug console.js works and implemented this in the consoleexport itself.

@LeHack
Copy link

LeHack commented Jan 15, 2016

Actually I'm thinking of a similar solution (for me FireBug also generates too much overhead when running automated tests), but I didn't yet do a full research on whether there's anything already done that could server the same functionality. If I don't find it, I'm planning to take a shot at it.

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

No branches or pull requests

2 participants