> I'm not sure changing behavior of the JS VM is the proper layer to > accomplish this. I think reporting messages from the JS console is a > better place to start. We could change the test harnesses to fail tests > if certain errors (like SyntaxError or TypeError) are raised. If there > is a "hook" in the JS VM to catch said errors at error time, we could > have the test harnesses run Firefox in a mode that makes said errors > more fatal (even potentially crashing as you suggest) and/or included > additional metadata, such as stacks.
Ok, I discussed this with jorendorff. It shouldn't be too hard to add this hook, plus it should have basically no overhead. The next step would be to register a test harness handler to crash (or do something else). This would later open the door to reporting errors (possibly through crashing) from Nightly, Beta, Release, ... My main worry, at this stage, is what we encountered when we started flagging uncaught async errors: some module owners simply never fixed their errors, so we had to whitelist large swaths of Firefox code, knowing that it was misbehaving. Cheers, David _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
