Closed Bug 127091 Opened 23 years ago Closed 23 years ago

Mis-reporting of secure sites when using tabbed browsing

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 101723

People

(Reporter: m, Assigned: trudelle)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.8) Gecko/20020204 BuildID: 2002020406 This bug causes the 'Page Info' window and the padlock icon to report incorrect security settings, depending upon which page was loaded into the first tab. This is an extension of bug 120043 ("Page info shows information about a page in the first tab") but with the following difference: if a secure page is loaded into the first tab and an insecure page loaded into the second, as expected by that bug, the second page is shown as secure. But then if the secure page is closed, so the insecure page moves into the first tab, this page is incorrectly reported as secure (with the certificate of the secure site that was closed). Reproducible: Always Steps to Reproduce: 1. Open a new browser window. 2. Make sure that in Preferences / Navigator / Tabbed Browsing, the check box "Control+Enter in the URL bar" is turned OFF. (So you can actually load a page into the first tab!) 3. Load a secure page into the first tab, e.g. https://secure.dabs.com 4. Open a new tab and load an insecure page, e.g. http://www.mozilla.org 5. Notice that the second tab has the glowing padlock icon, i.e. it is displaying the info from the first tab, as indicated by bug 120043 6. Switch to the first tab (the secure one) and close that tab. 7. Note that the glowing padlock icon is still present - we're leaving bug 120043 territory now. 8. Click the glowing padlock icon; notice that it suggests that www.mozilla.org is a secure site. 9. Click 'View' and you will see the certificate from secure.dabs.com (which was closed earlier). Similarly, you can load an insecure page in the first tab, and a secure one in the second tab; close the insecure one so the secure tab is first, and Mozilla suggests that the secure site (e.g. secure.dabs.com) is in fact insecure. Actual Results: The security info was "inherited" from the page that was first loaded into the first tab. Expected Results: The security information should be correctly updated when tabs are added or removed. This bug is almost certainly related to bug 120043.
Most likely a dupe of bug 101723.
I was about to say the same thing (mid-air collision). *** This bug has been marked as a duplicate of 101723 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.