Closed
Bug 134218
Opened 23 years ago
Closed 23 years ago
new tabbed windows do not display correct ssl information
Categories
(SeaMonkey :: Tabbed Browser, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 101723
People
(Reporter: mesostinky, Assigned: jag+mozilla)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.9+)
Gecko/20020314
BuildID: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.9+)
Gecko/20020314
If you open a window in a new tab, whenever you go to a ssl enabled site the new
tab does not display the correct security information for the new tabbed window.
It displays the security information for the parent tabbed window. For example I
have a second tabbed window open at www.newegg.com(it can be any ssl site).
After entering the ssl part of the site clicking on the security lock brings up
information for the parent window currently
http://www.mozilla.org/quality/help/bugzilla-helper.html. Instead it should
bring up the security info for https://www.newegg.com/app/orderstatus.asp which
is the page it is really on.
Reproducible: Always
Steps to Reproduce:
1.Open moz to any start page. (example www.google.com)
2.Open a new tab from a link on that start page.(ex any hyperlink from the front
page)
3.Go to any ssl site from the new tabbed windows(ex www.newegg.com)
4.enter a secured area of the new site on the tabbed window.
5.click on the security lock and see how it points to parent on not current
tabbed window.
Actual Results: Displays security info for parent in example it show security
for www.google.com, not security for https://www.newegg.com/app/orderstatus.asp.
Expected Results: Should show security certificate for newegg.com etc.
Can be reproduced from any start page. I have started at www.mozilla.org and
then opened a new tab and browsed to both yahoo and amazon secure aresa with the
same results. Since the browser is indeed at https I assume in fact the
transaction is secure but do not know if it is.
Comment 1•23 years ago
|
||
This problem has been fixed in recent nightlies.
*** This bug has been marked as a duplicate of 101723 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•