Closed Bug 844427 Opened 7 years ago Closed 7 years ago

New windows should maintain the openers private-browsing state

Categories

(Firefox :: Private Browsing, defect)

defect
Not set

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox19 --- unaffected
firefox20 - affected
firefox21 --- affected
firefox22 --- affected

People

(Reporter: jaws, Unassigned)

References

Details

(Keywords: ux-error-prevention)

As mentioned here, http://www.reddit.com/r/firefox/comments/191poi/firefox_beta_includes_per_window_private_browsing/c8k1s8s.

With new per-window private browsing, pressing Ctrl+N in a private browsing window will spawn a non-private browsing window.

For users who were accustomed to the previous implementation model, this behavior will cause a non-private window to be loaded, potentially leading to a mode-error with users accidentally visiting websites in a non-private window.

I am proposing that new windows, Ctrl+N/Cmd+N, be created using the openers private-browsing state. This is consistent with link context-menus that only feature a "Open Link in New Tab" and "Open Link in New Private Window" (note the lack of "Open Link in New Window").
This was an explicit decision in bug 819202, since keyboard shortcuts that behave differently based on context don't seem like a good idea. It's also in line with Chrome's behaviour.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.