Our team is in disagreement as to whether this is a good idea.
What are the possible pitfalls to turning this setting off? One member said that there is a risk that we will allow a number of errors into our code that might not work with some future browser. Then, instead of having a few errors here and there to correct, we will have a large backlog. Is this a legitimate fear?
Can anyone provide examples where ignoring minor JS errors causes larger problems down the road? Can anyone provide counter examples (that ignoring them has caused no issues)? I realize that you can't prove a negative, but a product that has adopted this policy with no problems through several browser version upgrades carries weight in our decision.
Edited to add: There are no user reported bugs for that specify they have used this setting. It is not a default setting, so most end users will not change it. But we are tasked with testing the code, so we turn it on to find all the bugs that we can. There is disagreement within the team as to whether this is a good practice. One side says we should find all the bugs we can and deploy the cleanest code that we can. The other side says that this is a minor issue and we should focus on larger issues (an opinion I can agree with). But the question is whether this policy of ignoring apparently minor errors will later cause larger problems, particularly with accelerated releases of browser versions.