Comment by akennberg

Can we get a properly working window.onerror? Currently we either get a very generic Script Error (0 information for debugging) or have to wrap every native method in one with a try/catch. This is more for error log collection and aggregation to understand what's breaking in production.