Open Bug 1027285 Opened 10 years ago Updated 2 years ago

Private Browsing and crtl+N

Categories

(Firefox :: Private Browsing, defect)

defect

Tracking

()

People

(Reporter: Stamimail, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release) Build ID: 20140605174243 Steps to reproduce: While Private Browsing, pressing crtl+N should open new window in Private Browsing. In the current situation, the user doesn't noticed that the Private Browsing was removed when he opened a new window. This is especially important for those who do not use tabs. I know also that in IE it works like I said.
Hi, thanks for taking the time to report a problem. I think that Ctrl+N intended behavior is only (and always) to open normal windows: you can open a new Private Browsing window with Ctrl+Shift+P. In addition to that, the user is able to always tell if (s)he's in Private Browsing mode just looking if there's the purple mask symbol on. IMO this is not a bug, but a design choice. I'm moving to Private Browsing component, though, so that the people of the relevant team can decide if a more explicit warning is needed when the user passes from Private to Normal browsing via Ctrl+N. Cheers, Francesca I agree though, that the passage from Private to non-Private browsing when using Ctrl+N to open a new window is something that could be made more visible to the user. The only way to tell that
Component: Untriaged → Private Browsing
(In reply to Francesca Ciceri [:madamezou] from comment #1) > > I agree though, that the passage from Private to non-Private browsing when > using Ctrl+N to open a new window is something that could be made more > visible to the user. The only way to tell that Forgot to delete this part, so that now my message sounds a bit schizophrenic -.- Please ignore these last lines :).
What appears to be true, sometimes differs from reality. I'm speaking from my experience...
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → All
Hardware: x86_64 → All
Version: 30 Branch → unspecified
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.