Hello Fabrice,

Merci pour la réponse à la vitesse de l'éclair. We are detecting the existence of the console using "window.console", but afterwards we test for the console capabilities. For instance the Safari console doesn't support console.debug. With CompanionJS installed our current logging wrapper crashes due to the capability test.

Is there a way to detect that the console is CompanionJS so that we can skip the capability testing?

Thank you Fabrice,

We'll go with the IE detection for now, thanks for the suggestion. Extra properties would be nice in 0.4.

You might find come across a fair amount of people with a similar problem though. If you google for:
"if (console.log"
"if (console.debug"
"typeof(console.log"
"typeof(console.debug"

There's a few interesting pages, for instance Dojo seems to do a fair bit of capability testing here:
http://trac.dojotoolkit.org/changeset/13755

and this version of firebugx.js was recently posted on the extjs forum to prevent null pointer errors on the safari console.debug:

(function(){
  // firebugx.js optimized for compressability and Safari
  var win = window, emptyFn = function(){}, names = ["log", "debug", "info", "warn", "error", "assert", "dir", "dirxml", "group", "groupEnd", "time", "timeEnd", "count", "trace", "profile", "profileEnd"];
  if (!win.console) {
    win.console = {};
  }
  var console = win.console;
  for (var i = 0; i < names.length; ++i) {
    if (!console[names[i]]) {
      console[names[i]] = emptyFn;
    }
  }
})();

OK, I found a possible solution :

I will add an option to either inject "console" in the window, or to inject javascript code to create a console object. On the second option, I will wrap the native C++ object into this js object so "if (console.log)" will work. This will inject some JS code into the window, but the code should not be very intrusive.

Tell me if you like this idea.