Closed Bug 845592 Opened 11 years ago Closed 11 years ago

New Private Window entry in File menu doesn't make sense in permanent private browsing

Categories

(Firefox :: Private Browsing, enhancement)

20 Branch
x86
macOS
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 22
Tracking Status
firefox20 --- verified
firefox21 --- verified
firefox22 --- verified

People

(Reporter: suishouen, Assigned: ehsan.akhgari)

Details

Attachments

(4 files)

Attached image Screenshot.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130220104816

Steps to reproduce:

1. Open "File Menu" when using normal browsing mode.
2. Open "File Menu" when using private browsing mode.



Actual results:

We see exactly the same "File Menu".


Expected results:

We expect different "File Menu" like as Opera Browser.
As Firefox tries to have dual mode windows and tabs, it needs dual mode "File Menu": for normal browsing mode and for private browsing mode.
So we can select "Normal Browsing" or "Private Browsing" from the "File Menu" in each of windows or tabs.

Screenshot is coming...
Severity: normal → enhancement
Component: Untriaged → Private Browsing
Eiichi, what differences are you actually looking for? All of the menu entries in the File menu make sense for both public and private browsing, so there's no point in hiding them.
Flags: needinfo?(suishouen)
(In reply to Josh Matthews [:jdm] from comment #1)
> Eiichi, what differences are you actually looking for?

1. Opera's Menu enables users to open a new tab in "Normal Mode" or "Private Mode" in the current window.
2. Opera's Menu enables users to open a new window in "Normal Mode" or "Private Mode" instead of the current window.

3. But Firefox's Menu can't do them.
Flags: needinfo?(suishouen)
Thanks for the suggestion, but I don't see any reason to limit the actions available to the user unnecessarily.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
(In reply to Josh Matthews [:jdm] from comment #3)
> Thanks for the suggestion, but I don't see any reason to limit the actions
> available to the user unnecessarily.

Only for the record;
When I set to "Always use private browsing mode" in the preferences, "New window" acts like "New Private Window".
That confused me.
Why does "New Window" open in the private mode not in the normal mode?
That's actually a good point. Let's focus on correcting that problem.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WONTFIX → ---
Summary: Firefox needs dual mode "File Menu": for normal browsing mode and for private browsing mode. → New Window entry in File menu doesn't make sense in permanent private browsing
Blocks: PBnGen
I think "New Private Window" is advisable to be dimmed when users set to "Always use private browsing mode" in the preferences.
When users set to "Always use private browsing mode" in the preferences, they have an assumption that "New Tab" means "New Private Tab" and "New Window" means "New Private Window".
Summary: New Window entry in File menu doesn't make sense in permanent private browsing → New Private Window entry in File menu doesn't make sense in permanent private browsing
I wouldn't block the release of the feature on this, though.
No longer blocks: PBnGen
same issue may also be relevant when right clicking on a link
(In reply to eyal gruss (eyaler) from comment #9)
> same issue may also be relevant when right clicking on a link

Screenshot when right clicking on a link
Attached patch Patch (v1)Splinter Review
Assignee: nobody → ehsan
Status: REOPENED → ASSIGNED
Attachment #721042 - Flags: review?(josh)
Comment on attachment 721042 [details] [diff] [review]
Patch (v1)

Review of attachment 721042 [details] [diff] [review]:
-----------------------------------------------------------------

I'm not a good reviewer here.
Attachment #721042 - Flags: review?(josh)
Attachment #721042 - Flags: review?(gavin.sharp)
For reference:

Now,
1. New Window (Command + N) opens the page that users set in "Preferences > General > When Firefox starts".
2. New Private Window (Shift + Command + P) opens the "about:private browsing".

When users set to "Always use private browsing mode" in the preferences, they know what permanent private browsing means.
Comment on attachment 721042 [details] [diff] [review]
Patch (v1)

>diff --git a/browser/base/content/test/browser_private_browsing_window.js b/browser/base/content/test/browser_private_browsing_window.js

>+        isnot(newWindow.label, newPrivateWindow.label, "New Window's label should be overwritten");
>+        isnot(newWindow.accessKey, newPrivateWindow.accessKey, "New Window's accessKey should be overwritten");
>+        isnot(newWindow.command, newPrivateWindow.command, "New Window's command should be overwritten");

These test descriptions need to be adjusted (s/should/shouldn't/).
Attachment #721042 - Flags: review?(gavin.sharp) → review+
Comment on attachment 721042 [details] [diff] [review]
Patch (v1)

[Approval Request Comment]
Bug caused by (feature/regressing bug #): PBnGen
User impact if declined: See the bug description.  This can cause confusion for users of permanent PB mode.
Testing completed (on m-c, etc.): Locally, patch includes a test case.
Risk to taking this patch (and alternatives if risky): Not very risky.
String or UUID changes made by this patch: None.
Attachment #721042 - Flags: approval-mozilla-beta?
Attachment #721042 - Flags: approval-mozilla-aurora?
Backed out because of a linux browser-chrome bustage: https://hg.mozilla.org/integration/mozilla-inbound/rev/8a1ef77e58f6
Holding off on approval unless it can land without issue on trunk - will revisit and watch for an update .
https://hg.mozilla.org/mozilla-central/rev/116a46d187fe
Status: ASSIGNED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 22
Attachment #721042 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment on attachment 721042 [details] [diff] [review]
Patch (v1)

Looks like this landed ok now - approving for beta uplift so we can get this in tomorrow's fifth week beta build.
Attachment #721042 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Verified as fixed on Firefox 20 beta 6 (20130320062118), Mac OSX 10.7.5 and Windows 7:
Mozilla/5.0 (Windows NT 6.1; rv:20.0) Gecko/20100101 Firefox/20.0
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
On Firefox 20 beta 6 (20130320062118), Mac OSX 10.7.5;
1. Click "New Private Window" of File Menu opens the "about:private browsing".
2. "Command + N" shortcut opens the page that users set in "Preferences > General > When Firefox starts".
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This is another bug Eiichi. It existed before this bug got fixed.

Please file it separately.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
(In reply to Ioana Budnar [QA] from comment #27)
> This is another bug Eiichi. It existed before this bug got fixed.
> 
> Please file it separately.

Sorry, I filed Bug 853996.
Verified as fixed on:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Firefox/21.0
The bug is Verified fixed on Firefox Aurora 22.0a2 – 20130407004016: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20130407 Firefox/22.0

but if I use the single right click on the Firefox (20/21/22) dock icon on Mac OS X there is the "New Window" and the "New Private Window" menu even if in permanent private browsing and the "New Window" opens a private window since we are in the permanent private browsing.

The point whom  I was thinking about is: "If the "New Window" entry in File menu doesn't make sense in permanent private browsing, why it does in the dock menu?"
It doesn't. Feel free to open a new bug for that!
mass remove verifyme requests greater than 4 months old
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: