@BigMax
Yes, we can hook that - but processing the resultant data yields
tons of errors, the vast majority of them nonfatal or in extensions (some of which leak into browser JS space). For reference last time I enabled collection of all errors in the browser we had something along the lines of a few hundred error reports a
minute, 99% of which we could do absolutely zilch about. (To clarify: we do actually wrap all our application code and logic in try/catch blocks with server-notifying error handlers, so this is something in one of our dependencies)
As for the bug - okay, we’ll try and reproduce it and figure out what’s going on. Sadly we minify/compress all our production JS so it’s a bit more complex than just looking where that says but we’ll get it sorted.
Edit: We think we’ve fixed it now. Please shout if not. We’ve certainly fixed a couple of bugs impacting IE < 9 and forum spoilers, if nothing else, and added a friendly message to help people on browsers that were last up-to-date approximately the same time that fish grew legs download a more modern browser.
