Closed Bug 517791 Opened 15 years ago Closed 14 years ago

browser chrome test: browser_privatebrowsing_openlocation.js | The correct URL should be loaded via the open location dialog - Got about:logo, expected about:buildconfig

Categories

(Firefox :: Private Browsing, defect)

3.5 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 3.7a5

People

(Reporter: MatsPalmgren_bugz, Assigned: ehsan.akhgari)

References

()

Details

(Keywords: intermittent-failure, Whiteboard: [fixed by bug 541404])

Linux mozilla-1.9.1 unit test on 2009/09/20 12:28:51
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.5/1253474931.1253479249.29787.gz

TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/components/privatebrowsing/test/browser/browser_privatebrowsing_openlocation.js | The correct URL should be loaded via the open location dialog - Got about:logo, expected about:buildconfig


(similar to bug 513420?)
Whiteboard: [orange]
Blocks: 438871
This bug will be fixed by my patch in bug 541404.
Assignee: nobody → ehsan
Status: NEW → RESOLVED
Closed: 14 years ago
Depends on: 541404
Resolution: --- → FIXED
Whiteboard: [orange] → [orange][will be fixed by bug 541404]
Hmm, I marked it as FIXED by mistake.  :(
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Whiteboard: [orange][will be fixed by bug 541404] → [orange][fixed by bug 541404]
Target Milestone: --- → Firefox 3.7a5
Flags: in-testsuite-
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.5/1277396552.1277397137.18854.gz
Linux mozilla-1.9.1 test mochitest-other on 2010/06/24 09:22:32
s: moz2-linux-slave08

TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/components/privatebrowsing/test/browser/browser_privatebrowsing_openlocation.js | The correct URL should be loaded via the open location dialog - Got http://example.org/, expected about:blank
Whiteboard: [orange][fixed by bug 541404] → [fixed by bug 541404]
You need to log in before you can comment on or make changes to this bug.