Closed Bug 121353 Opened 23 years ago Closed 23 years ago

unsecure page secure?

Categories

(Core :: Security, defect)

Sun
Solaris
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 101723

People

(Reporter: mike.s, Assigned: paulkchen)

References

()

Details

This may be a fork of 57395 or 58898. But maybe not as it's not really related
with dynamic skin changing. More with new tabs...

Scenario:
I use the modern skin
go to what should be a secure site (https://dstore.com.au/account/)
the lock didn't close
clicking on the lock brings up the security dialog which says the transmission
has not been encrypted
tried to change skin to classic but browser crashed..
started browser changed to classic skin
go back to secure site (https://dstore.com.au/account/)
lock closes
change back to modern skin
lock stays closed
open up new tab at non encrypted site
lock stays closed
exit browser
start browser (in modern skin)
go to secure site (https://dstore.com.au/account/)
lock closes
open up new tab at non encrypted site
lock stays closed
clicking on it brings up the security info for the secure site.
open up a new browser window and lock is open.


It seems that if the very first time you go to a secure site the skin is the
modern skin the lock doesn't close untill you visit a secure site (any secure
site) in the classic skin. Once you've visited a secure site in a classic skin
subsequent visits to secure sites, in any skins, it does close. BUT it doesn't
open back up for new tabs. 

Now apparently this was fixed. As of bug 57395 (cira.Nov 2000). I'm running a
nightly build (15 Jan 2002) and it's still occuring.

miKe@sauron:~ :2 >/usr/local/mozilla/mozilla --version
Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.7+) Gecko/20020115, build
2002011510

mike
Duplicate of 'tabbrowser: "security" (SSL) info/button/icon/padlock in the
status bar only reflects first tab/page'

*** This bug has been marked as a duplicate of 101723 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verifying
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.