VERY confused - javascript not being executed - unless Console is turned on in Firebug?

You are calling some method on console in your JavaScript is my best guess. Chrome has console defined be default, so it is not a problem On Firefox, however, there is no such global object (not without Firebug), so when you try to call a property on an undefined object like console. Log(..) it throws an exception which you are not catching, so the JavaScript execution halts.

You are calling some method on console in your JavaScript is my best guess. Chrome has console defined be default, so it is not a problem. On Firefox, however, there is no such global object (not without Firebug), so when you try to call a property on an undefined object like, console.

Log(..); it throws an exception which you are not catching, so the JavaScript execution halts.

Wow. That could very will be it. A friend of mine just told me to use console.

Log because it was awesome, and it seemed so! I shall try this theory of yours right now! – shawnjan Jul 15 '10 at 21:43 You are the man ;) – shawnjan Jul 15 '10 at 21:46 I can't accept the answer for 4 minutes, but I will.

– shawnjan Jul 15 '10 at 21:46 It's best to define it yourselves if it's not already available. Ideally you wouldn't want console. * in a production app, but then again it's easy to change the behavior of a custom object to start sending logs/errors to a remote server with the flip of a switch.So console logs are good, but have a backup plan embedded in your scripts, or just overwrite the whole thing and in development mode send it to the native console (if exists), or remote server for production.

– Anurag Jul 15 '10 at 21:53.

You're probably calling a method of the console object which just doesn't exist by default in most web browsers. It may be always available on webkit based browsers (like Chrome) but with firefox/IE(/opera? ) it requires an external add-on, either firebug or a javascript dependency.

Checkout things like firebugx which simply defines the most common methods of a console object as no-op functions.

You are calling some method on console in your JavaScript is my best guess. Chrome has console defined be default, so it is not a problem.

You're probably calling a method of the console object which just doesn't exist by default in most web browsers. It may be always available on webkit based browsers (like Chrome) but with firefox/IE(/opera?) it requires an external add-on, either firebug or a javascript dependency.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.