http://brasstacks.mozilla.com/topfails/test/SeaMonkey?name=chrome://mochikit/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js 2 on 2010-08-27 http://brasstacks.mozilla.com/topfails/test/SeaMonkey?name=chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js 5 on 2010-10-07 then from 2010-10-26 to 2010-10-30 (= now) http://brasstacks.mozilla.com/topfails/test/SeaMonkey?name=chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug562797.js from 2010-10-26 to 2010-10-30 (= now) { TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug562797.js | Should be on the right view - Got list-view, expected detail-view TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug562797.js | Back button should have the right state - Got false, expected true TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug562797.js | Forward button should have the right state - Got true, expected false ... TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug562797.js | Should be on the right view - Got list-view, expected detail-view TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug562797.js | Back button should have the right state - Got false, expected true } On my local Windows 2000, with an Opt tinderbox-build, the one in "browser-window" fails, [as with our 3 Debug t-b :-|] the one in "browser" passes. [wheras our Debug Windows t-b doesn't :-/]

Pushed to mozilla-central http://hg.mozilla.org/mozilla-central/rev/9d848c9a0d9d btw: I verified this fixes the tests on SeaMonkey locally.

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1288658545.1288661027.27190.gz Linux comm-central-trunk debug test mochitest-other on 2010/11/01 17:42:25 V.Fixed

hmm. not sure if this is exactly the same (since this is seamonkey)

It is very likely not the same bug... please file a new one

Take that back, I believe this is fixed by changeset 0f10a0099dfc

yup. my fault. please ignore the last few comments.