Closed Bug 575289 Opened 14 years ago Closed 14 years ago

Difficult to differentiate Normal Browsing from Private Browsing on New Windows Theme

Categories

(Firefox :: Theme, defect)

All
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 588655
Tracking Status
blocking2.0 --- final+

People

(Reporter: tetsuharu, Unassigned)

References

Details

(Keywords: regression)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; WOW64; en-US; rv:1.9.3a6pre) Gecko/20100628 Minefield/3.7a6pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; WOW64; en-US; rv:1.9.3a6pre) Gecko/20100628 Minefield/3.7a6pre On Firefox 3.6, We can discern Private Browsing Mode from Normal Browsing Mode with to show the mode in title bar. But on Firefox 4 new Windows Theme, no sign of Private Browsing or Normal browsing in title bar. And there is not Private Browsing displaying in latest Windows Theme Mockups (https://wiki.mozilla.org/Firefox/4.0_Windows_Theme_Mockups). I think that, the user confusion happen if there is no displaying to individuate browsing mode. Reproducible: Always
Blocks: 544820
Version: unspecified → Trunk
Attached image Private Browsing Mockup (deleted) —
I noticed this as well. I don't think we should ship Firefox 4 like this.
Status: UNCONFIRMED → NEW
blocking2.0: --- → ?
Ever confirmed: true
Status: NEW → UNCONFIRMED
blocking2.0: ? → ---
Ever confirmed: false
Arrg, why does bugzilla do that - when I cc'd myself it set it to 'unconfirmed', setting back to "new"
Status: UNCONFIRMED → NEW
Ever confirmed: true
Related to/Dupe of Bug 513418?
I'd say 513418 is a possible fix for this. This is a regression from drawing in the titlebar though, since you used to be able to look at the window title and see "(Private Browsing)".
blocking2.0: --- → ?
Depends on: 513418
Keywords: regression
(In reply to comment #5) > I'd say 513418 is a possible fix for this. This is a regression from drawing in > the titlebar though, since you used to be able to look at the window title and > see "(Private Browsing)". This is a dupe of bug 513418, as far as I can see.
We could presumably fix this in some other way. Also, that bug is not a regression whereas this one is. As long as we recognize those two facts, I don't really care what happens with this specific bug.
At least blocking final, but we probably want to fix it before hand.
blocking2.0: ? → final+
I think a kind of subtle and simple way to do this in the short-term would be to put the mask in the firefox button and change that button to purple in private browsing mode.
As a temporary solution we might add PB icon into tab bar when PB is active.
(In reply to comment #10) > As a temporary solution we might add PB icon into tab bar when PB is active. I think that would be as much work as changing the Firefox-button, so let's get the proper solution in there instead. If I only knew how to create patches and build Firefox with them, then I could do it myself (or at least try).
(In reply to comment #11) > If I only knew how to create patches and > build Firefox with them, then I could do it myself (or at least try). https://developer.mozilla.org/En/Developer_Guide
>I think a kind of subtle and simple way to do this in the short-term would be >to put the mask in the firefox button and change that button to purple in >private browsing mode. I was thinking purple button with "Firefox (Private)" the icon might be had to pull off at 16x16. Either way, in addition to the button change we are also hoping to pick up something like bug 513418, although darkening the theme is opportunistic.
(In reply to comment #13) > although darkening the theme is opportunistic I'm finding this mockup very attractive.
I guess this bug should also depend on bug 588655?
Status: NEW → RESOLVED
Closed: 14 years ago
No longer depends on: 513418
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: