Component: Security Assurance → Location Bar
Product: mozilla.org → Firefox
QA Contact: security-assurance → location.bar
Version: other → Trunk
I'm worried that making "https" black will make it harder to pick out the domain name. I'd prefer making "https" blue or green.
How about we just leave it as is? The fact that we show https:// at all while hiding http:// is already an emphasis, and more importantly, there's the lock icon.
6 years ago
(In reply to Jesse Ruderman from comment #1) > I'd prefer making "https" blue or green. +1 for blue, green is for HTTPS+EV according to bug 747085. (In reply to Dão Gottwald [:dao] from comment #2) > more importantly, there's the lock icon. beltzner has raised some, very valid IMHO, concerns on "the return of the padlock" at https://groups.google.com/d/topic/mozilla.dev.apps.firefox/ODX1PJutsLM/discussion you might be interested in joining the discussion there.
Before the new design, the site identity button was blue for the non-ev case (https://support.mozilla.org/en-US/kb/Site%20Identity%20Button#w_blue-basic-identity-information), however probably it's better to let it be black (otherwise less aware people wouldn't understand the difference between blue and green!)
Created attachment 621132 [details] [diff] [review] Patch for bug The security team requested that we darken the https:// portion to make it easier to see that the connection is over SSL during the security review. This patch makes domain-verified connections have a black https://. Tests to follow.
Created attachment 621133 [details] [diff] [review] Tests for patch
(In reply to Dão Gottwald [:dao] from comment #2) > How about we just leave it as is? The fact that we show https:// at all > while hiding http:// is already an emphasis, and more importantly, there's > the lock icon. I agree with Dão. We are going to make the lock darker also. I don't think it needs more emphasis than that.
Comment on attachment 621132 [details] [diff] [review] Patch for bug Clearing review since it looks like we don't want to do this anymore.
Resolving as WONTFIX based on the comment #1, comment #2, and comment #7.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.