Closed Bug 1083045 Opened 5 years ago Closed 5 years ago
Scratchpad tests shouldn't depend on chrome debugging being disabled by default
It's a common mistake to assume the world will always stay the same. Alas, as the oldest among us can attest, it never does.
Alex posted a patch for this in bug 1072181 comment 9, which I've moved to this bug and reviewed.
Attachment #8505282 - Flags: review+
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 36
Comment on attachment 8505282 [details] [diff] [review] scratchpad-tests.patch Approval Request Comment [Feature/regressing bug #]: it's a test improvement that will be required once we uplift some other patches that will make the failures permanent [User impact if declined]: none, only test failures [Describe test coverage new/current, TBPL]: existing tests [Risks and why]: none, it's a test-only change [String/UUID change made/needed]: none
Comment on attachment 8505282 [details] [diff] [review] scratchpad-tests.patch TIL: no approval required for test-only fixes.
You need to log in before you can comment on or make changes to this bug.