The private browsing option should be only visible for developers and not for general consumer use. By default in partner builds the private browsing options have to be invisible. In a future release, once we have defined and agreed UX input, we can develop those features and then enable the feature.
What's the justification for this change?
(In reply to Fabrice Desré [:fabrice] from comment #1) > What's the justification for this change? We need proper UX for it and v3 is currently higher priority for them.
What's not proper in the current UX?
(In reply to Fabrice Desré [:fabrice] from comment #3) > What's not proper in the current UX? We don't know since we can't get UX review.
I remember one of the issues is that the indication of private browsing is done by colouring the rocket bar, something which applications and web content are free to do
I still don't understand why we didn't do a simple spec for this. We had plenty of time here, and had an opportunity to bring a great feature to the OS. We are not going to be able to innovate if we can't even land simple features like this.
Assignee: nobody → kgrandon
Status: NEW → ASSIGNED
(In reply to Dale Harvey (:daleharvey) from comment #5) > I remember one of the issues is that the indication of private browsing is > done by colouring the rocket bar, something which applications and web > content are free to do It would be trivial to change this to either prevent sites from doing that in private windows, or changing the UX in some other way. I'm currently looking at hiding this behind a setting. Doing some UX tweaks would be less work and a smaller change though.
So don't add yet another setting. That's madness. I have my finger on the backout button ;)
It seems we have a spec for this, so let's try to get it in. If we don't finish we can revisit this.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.