Closed Bug 1449925 Opened 2 years ago Closed 2 years ago
The --private command line parameter doesn't work when browser
.startup .blank Window is true
When browser.startup.blankWindow is true, there's already an about:blank window that exists by the time the command line parameter is processed.
When encountering the -private flag, this makes the existing navigator:blank (about:blank) window become private. I'm removing the warning that was added in bug 800193 because: - now that add-ons no longer have xpcom access, there's only internal code that can all this. - bug 1318388 made this safer (by requiring that only about:blank has been loaded before we call this setter).
Attachment #8963579 - Flags: review?(ehsan)
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/658361dcadf3 make the --private command line parameter work when browser.startup.blankWindow is true, r=Ehsan.
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/a04b1417861b follow-up to fix conflict with bug 1450242, rs=bustage-fix, a=bustage-fix on CLOSED TREE
You need to log in before you can comment on or make changes to this bug.