title: Enable/Disable console.log in production version
body: <p>Based on a flag I want to enable or disable the <code>console.log</code> in the production versions. But I don't want to expose that option to my users because then everyone will ask about it and waste my time.</p>
  
  <p>If I allow such flag to be stored in user preferences thru the <em>Options</em> dialog, till those preferences are loaded, my code will be spewing out the <code>console.log</code> output till that flag is loaded from the chrome storage.</p>
  
  <p>I can create a debug flag cookie using extensions but unfortunately my extension works on many sites.</p>
  
  <p>If I disable <code>console.log</code> altogether in production versions but when clients face problem then at that moment I'll not be able to look into the <code>console.log</code> to debug it. So this is not feasible.</p>
  
  <p>Is there any what my extension can know from the first line that console.log needs to be bypassed or not every time the extension is run( includes <em>BG script</em>, <em>content script</em> and the <em>options</em> dialog)?</p>