4 ms·

The console api isn't really linked to chrome. I prefer the chrome debugging tool but those things should work on firefox too. I think you could be clearer on t

by soyuka 12y ago

The console api isn't really linked to chrome. I prefer the chrome debugging tool but those things should work on firefox too. I think you could be clearer on this point.

tajen 12y ago
Don't use that in prod, because it doesn't work in IE and it will cause your js to stop working. In IE the 'console' object doesn't even exist if the developer tools aren't displayed, so if you use "console.log" in your program, your js will just throw an NPE. Note that if you try closing the Developer Tools, 'console' is still declared for this page and all descendant pages. To test 'console.log' you need to avoid opening the devtools and open a new tabs.
- cleverjake 12y ago
  that hasn't been the case since IE 9
  - tajen 12y ago
    This person is reporting it for IE10, do you have more insights? Do you think his IE was in compatibility mode? http://stackoverflow.com/questions/18480948/ie-10-debug-console-f12-changes-behavior http://stackoverflow.com/questions/18480948/ie-10-debug-cons...
    - cleverjake 12y ago
      yep. compat mode.
- deanclatworthy 12y ago
  The simple solution is to polyfill: https://github.com/paulmillr/console-polyfill https://github.com/paulmillr/console-polyfill
  - ux-app 12y ago
    Another solution is to remove all debug commands as part of your build/deploy process.
- rmchugh 12y ago
  too right, extremely annoying bug, because when you open the dev tools to debug it, it starts working again!
- ahoge 12y ago
  > Don't use that in prod A linter will catch this.
- Encosia 12y ago
  I don't remember when exactly, but they fixed that at some point. I just ran this simple test in IE (without ever opening the dev tools) and got the alert: http://jsbin.com/hodavocuwu/1/edit http://jsbin.com/hodavocuwu/1/edit
ndesaulniers 12y ago
Indeed, all of these are in Firefox, in Nightly at least. Though console.profile and console.profileEnd didn't seem to work? I'm sure someone from FF dev tools will turn up in this thread to clarify.
- jsantell 12y ago
  time/timeEnd, profile/profileEnd all work in Firefox up to Aurora -- current nightly has a new performance tool that will support profile/profileEnd in a few days, and will most definitely have it before uplift to Aurora https://bugzil.la/1077464 https://bugzil.la/1077464

by soyuka 12y ago

The console api isn't really linked to chrome. I prefer the chrome debugging tool but those things should work on firefox too. I think you could be clearer on this point.

tajen 12y ago

Don't use that in prod, because it doesn't work in IE and it will cause your js to stop working. In IE the 'console' object doesn't even exist if the developer tools aren't displayed, so if you use "console.log" in your program, your js will just throw an NPE. Note that if you try closing the Developer Tools, 'console' is still declared for this page and all descendant pages. To test 'console.log' you need to avoid opening the devtools and open a new tabs.

cleverjake 12y ago
that hasn't been the case since IE 9
- tajen 12y ago
  This person is reporting it for IE10, do you have more insights? Do you think his IE was in compatibility mode? http://stackoverflow.com/questions/18480948/ie-10-debug-console-f12-changes-behavior http://stackoverflow.com/questions/18480948/ie-10-debug-cons...
  - cleverjake 12y ago
    yep. compat mode.
deanclatworthy 12y ago
The simple solution is to polyfill: https://github.com/paulmillr/console-polyfill https://github.com/paulmillr/console-polyfill
- ux-app 12y ago
  Another solution is to remove all debug commands as part of your build/deploy process.
rmchugh 12y ago
too right, extremely annoying bug, because when you open the dev tools to debug it, it starts working again!
ahoge 12y ago
> Don't use that in prod A linter will catch this.
Encosia 12y ago
I don't remember when exactly, but they fixed that at some point. I just ran this simple test in IE (without ever opening the dev tools) and got the alert: http://jsbin.com/hodavocuwu/1/edit http://jsbin.com/hodavocuwu/1/edit

ndesaulniers 12y ago

Indeed, all of these are in Firefox, in Nightly at least. Though console.profile and console.profileEnd didn't seem to work? I'm sure someone from FF dev tools will turn up in this thread to clarify.

jsantell 12y ago
time/timeEnd, profile/profileEnd all work in Firefox up to Aurora -- current nightly has a new performance tool that will support profile/profileEnd in a few days, and will most definitely have it before uplift to Aurora https://bugzil.la/1077464 https://bugzil.la/1077464