rem: *       1) ideally, the notification would disappear when the document that had the *          error was flushed. how do I know when this happens? All the nsIScriptError *          object I get tells me is the URL. Where is it located in the content area? *       2) the notification service should not display chrome script errors. *          web developers and users are not interested in the failings of our shitty, *          exception unsafe js. One could argue that this should also extend to *          the console by default (although toggle-able via setting for chrome authors) *          At any rate, no status indication should be given for chrome script *          errors. 
add: *       1) ideally, the notification would disappear when the *       document that had the error was flushed. how do I know when *       this happens? All the nsIScriptError object I get tells me *       is the URL. Where is it located in the content area? *       2) the notification service should not display chrome *       script errors.  web developers and users are not interested *       in the failings of our shitty, exception unsafe js. One *       could argue that this should also extend to the console by *       default (although toggle-able via setting for chrome *       authors) At any rate, no status indication should be given *       for chrome script errors. 
context: function initConsoleListener(){  /**   * XXX - console launch hookup requires some work that I'm not sure how to   *       do.   *   *       1) ideally, the notification would disappear when the document that had the   *          error was flushed. how do I know when this happens? All the nsIScriptError   *          object I get tells me is the URL. Where is it located in the content area?   *       2) the notification service should not display chrome script errors.   *          web developers and users are not interested in the failings of our shitty,   *          exception unsafe js. One could argue that this should also extend to   *          the console by default (although toggle-able via setting for chrome authors)   *          At any rate, no status indication should be given for chrome script   *          errors.   *   *       As a result I am commenting out this for the moment.   *  var consoleService = Components.classes["@mozilla.org/consoleservice;1"]                                 .getService(Components.interfaces.nsIConsoleService);  if (consoleService)    consoleService.registerListener(consoleListener);  */}
meta: 9421	/local1/tlutelli/issta_data/temp/all_js/javascript/2006_temp/2006/9421/912f22f160396bc7d1c7e0a0f61716475667e226/navigator.js/clean/suite/browser/navigator.js