elaborate a little, please.  Is the goal so that the error console can still handle things in a more structured way than us just dumping console.error, or a way to get the error propagated to onerror without causing collateral damage?  In my limited web console noodling, it seems like Firefox actually likes console.log(ex) more than 'throw ex', but that was at the top-level of the web console where I created an error in there via 'new Error()' myself.  Chrome, on the other hand really liked the throw and hated me trying to console.log the exception, for which it just displayed a boring "Error {}" thing.