To move from a secure page to one that is not in the bar url leaves the color that is secure.

RESOLVED INCOMPLETE

Status

()

Firefox
Security
RESOLVED INCOMPLETE
10 years ago
8 years ago

People

(Reporter: Guillermo, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: DUPEME?)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5

	
When you visit a page with safety certificate, comes in the address bar of another colour url ...

If you are in a tab on a page with safety certificate, as http://mail.google.com and raisins to another tab in which you are on a page without safety certificate, as http://google.com for about hundredths of a second, still leaving the same color, which can lead to mistakes or deception.
This happens in all themes

----
Translation by the Google translator (http://www.google.es/translate_t)

Reproducible: Always

Steps to Reproduce:
1- Go to a secure page, such as mail.google.com
2- In another tab, opens a page is not safe, as google.com
3- Pass quickly from secure page to which it is not, you will see that over half a second, the page is not safe in the address bar color as if it were safer. That was not the case in the version 2.0 of Firefox
Actual Results:  
The tab page unsecured leaves with color if it were. The same happens if it is just the opposite: page appears as safe if not

Expected Results:  
It is a failure of this original version of Firefox
Whiteboard: DUPEME?
Not a security sensitive bug report that needs to stay hidden.

Do you have any addons install that could be making the transition slower?
Group: security
Resolving unconfirmed bugs older than a year with no activity as INCOMPLETE.  Please reopen or file a new bug if you can still reproduce the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.