Laurakeet wrote: > If I am using console.log for debugging locally do I need to make sure > I remove those statements once I have pushed my code to a live web > page? What if random users don't have firebug? Will it break my forms > or other pages? > > thanks, > Laura > > > > > yeah, its prolly a good idea to remove those. there are some spiffy txt editors which can find and remove nodes of htm and such, i think crimison editor has a feature like this, its nice cuz it searches for text within multiple files using wildcards and like. leaving the code in there wont break anything, but i have seen firefox and IE throw some random errors on console logging stuff.
for more complex apps, you can make a console.log wrapper function which calls this, then inside this wrapper function put a conditional to check if debug mode is on or off. So when you go to deploy onto production you can just toggle that boolean off, and it shouldn't spit that code out to your end users. Generally i just make it a habbit to remove all of it, as its not needed and wastes cpu cycles, and bytes. k --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
