User blog comment:Kirkburn/Technical Update: March 25, 2015/@comment-24473195-20150327161427/@comment-24473195-20150331100933

That's a good point about false positives. Perhaps a better alternative would be to have some sort of pop-up notification informing the user about potential errors. Something that could be disabled the same way we can disable "error checking" using modules.

Another idea is to automatically categorize pages with javascript errors (including false positives). This seems important because the errors exposed by the changes to the visual editor show that there are a lot of old javascript pages with considerable syntax/logical errors.

These kinds of errors also waste considerable staff/contributor time, because admins are the only ones able to make/revert changes to javascript pages (assuming they don't save in the main namespace). In the event of stubborn or absent admins these errors can persist for considerable time and cause problems for everyone.

So having a category for this would be perfect, in my opinion.