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

Mainting support #1

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
Open

Mainting support #1

wants to merge 7 commits into from

Conversation

TiTi
Copy link

@TiTi TiTi commented Dec 8, 2010

Hi,

This commit fix makes your logger works again with most current consoles :
-latest stable firebug (1.6)
-chrome console (v8 stable)
-IE8 dev tools
-opera
-firebug lite

I'm also planning to add more stuff soon, like:
-An hidden div on the page if no console available at all or if an option is setted.
Or at least a "tail".
-A way to export the history

Cheers and thx for your great jquery plugins!

@cowboy
Copy link
Owner

cowboy commented Dec 9, 2010

What exactly is the problem in current browsers? Do you happen to have a list of side-effects or errors that are occurring?

@TiTi
Copy link
Author

TiTi commented Dec 9, 2010

On your example page : http://benalman.com/code/projects/javascript-debug/examples/debug/

Firefox 3.6.12 with Firebug 1.6.0 (current stable release) : "this.trace is not a function"
=> even stop js execution!
This is because the first parameter of .apply should not be window but console

Opera doesn't use console.log/warn/... for now but opera.postError

I also had an issue with Chrome 7 but they recently upgrade to version 8 (stable branch) and the error doesn't appears anymore it seems (objects weren't correctly logged, strings were).

@cowboy
Copy link
Owner

cowboy commented Dec 25, 2010

Hmmn.. I'm not seeing any problems in Opera, I've tried in 10.63 and 11.0. What versions are you experiencing this issue in?

@TiTi
Copy link
Author

TiTi commented Dec 26, 2010

Yep that's because they updated Opera DragonFly: http://my.opera.com/dragonfly/blog/2010/12/03/getting-opera-dragonfly-ready-for-opera-11 (see: "Updated Command Line" -> was not working before).
Because of the way opera dragonfly works, you've got the latest dragonfly in 10.63 or 11.0: see "always up to date" on this page http://www.opera.com/dragonfly/ . Or go to "Developer Tools" in opera:config. Another link: http://dev.opera.com/articles/view/introduction-to-opera-dragonfly/

Well thank you for bringing this to my attention I didn't noticed the console.log/info/debug/error is now working in dragonfly.
I guess there is no more need to use opera.postError (which was the only "proper" logger in opera).
I'm gonna make some modifs soon on my repo.

@cowboy
Copy link
Owner

cowboy commented Dec 26, 2010

Awesome. I'm in the process of a full rewrite of this, actually. I'll post it as soon as I have something good!

…h .log, ...)

-Join array if apply not available (IE...)
@pboling
Copy link

pboling commented Apr 10, 2013

👍

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.

3 participants