Closed Bug 700190 Opened 8 years ago Closed 8 years ago
Attachment #572357 - Flags: review?(justin.lebar+bug)
I think waitForClipboard changed. Which is good, because it was silly to make code QI like this. But it's bad that the test harness didn't catch this failure. I guess the reason that this failure didn't cause the tree to burn is that the exception was inside checkClipboard? If we throw an exception outside checkClipboard, does the test fail? r=me if exceptions in general cause this test to fail. Otherwise, we need a bigger hammer.
Attachment #572357 - Flags: review?(justin.lebar+bug) → review+
I inserted |throw("foobar")| at the top-level of the JS code and this shows up in the console: TEST-INFO | unknown test url | [SimpleTest/SimpleTest.js, window.onerror] An error occurred: uncaught exception: foobar at :0 but the test still passes. I could wrap everything in the try-block but it seems like the test framework should catch this.
bz tells me that chrome tests swallow uncaught exceptions. See bug 652494.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla11
You need to log in before you can comment on or make changes to this bug.