Closed Bug 160195 Opened 23 years ago Closed 20 years ago

New tab of secure site gives security warning

Categories

(Core Graveyard :: Security: UI, defect, P3)

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 156758

People

(Reporter: lsof, Assigned: KaiE)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020618 BuildID: 20020618 When a new tab is opened, and a secure site from the personal toolbar is visited a security warning displays. Reproducible: Always Steps to Reproduce: 1. Open new tab. 2. Click secure site in Personal Toolbar. 3. Security warning displays. Actual Results: Warning shown. Expected Results: No warning shown.
xp apps.
Assignee: law → sgehani
Status: UNCONFIRMED → NEW
Component: QuickLaunch (AKA turbo mode) → XP Apps
Ever confirmed: true
QA Contact: gbush → paw
i don't understand. can you please provide *detailed* steps for normal (windowed) browsing and tabbed browsing and show how they differ such that you decided to file this bug?
A bookmarked item should not give a warning about the site being secure - the user already expects this.
We already agree, but we were unsure what exactly you do when you see that effect. However, I now suspect what happens: - you visit a secure site - you choose "open new tab" which opens a new tab with a blank page (as you can see, the blank page is not coming from a secure site, the lock is open) - you now go to a secure site - you see a message about entering a secure site Each tab is absolutetly independent. You can display https in one, and http in another. Therefore, each tab has its own "current security state". This is reflected when you change tabs. You'll see the lock icon change. The security warning always belongs to the currently displayed tab. I'd say we should keep this behaviour and mark this bug as wontfix. But note there is a similar bug and we are likely to fix that other one: bug 156758
Assignee: sgehani → kaie
PSM
Component: XP Apps → Client Library
Priority: -- → P3
Product: Browser → PSM
QA Contact: paw → junruh
Version: other → 2.4
Nobody disagreed with my previous comment, therefore I'm marking this as wontfix.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Verified.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Wontfix? Bug 156758 is effectively a generalisation of this one. So what sense would it make to fix that but not this?
The consensus over at the cluster of dupes seems to be that this should be fixed.
Status: VERIFIED → REOPENED
Resolution: WONTFIX → ---
*** This bug has been marked as a duplicate of 156758 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago → 20 years ago
Resolution: --- → DUPLICATE
Version: psm2.4 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.