[Cosmo-dev] JS error-handling in the UI

[Matthew Eernisse]

Two reasons:

1. Consistency. Right now all generic JS errors generated by the UI code 
  log to the console.

2. Efficiency/usability. Waiting for the modal dialog to pop, clicking 
the details link, popping up a new window, and scrolling to see all the 
stack is makes it much slower to do iterative debugging -- which is 
something I spend a lot of time doing. The Firebug error console has a 
lot of niceties for both logging and viewing errors all in one place 
that makes it much better for debugging than our home-rolled solution 
(with all due respect to the work you've done to make it more usable).

Now, if later we decide we'd like to design something that handles all 
errors in a unified way (e.g., hiding all of them behind the modal 
dialog facade we have now), and it's something that can be easily and 
permanently disabled in the dev environment to allow use of normal 
debugging tools, I'd be all for it.


M.

Bobby Rullo wrote:
> So why is that behavior desirable? The point of addErrback is that it 
> handles errors...why do you want stuff going to the console?
> 
> bobby