Closed Bug 1168461 Opened 5 years ago Closed 5 years ago

[Control Center] Implement different connection security states below the host name

Categories

(Firefox :: General, defect, P1)

defect
Points:
3

Tracking

()

VERIFIED FIXED
Iteration:
41.3 - Jun 29
Tracking Status
firefox41 --- verified

People

(Reporter: ttaubert, Assigned: ttaubert)

References

Details

(Whiteboard: [fxprivacy])

No description provided.
Depends on: 1146282
Points: --- → 3
Flags: qe-verify+
Flags: firefox-backlog+
Whiteboard: [fxprivacy]
Blocks: 1146282
No longer depends on: 1146282
No longer blocks: 1146282
Depends on: 1146282
Assignee: nobody → ttaubert
Status: NEW → ASSIGNED
Iteration: --- → 41.2 - Jun 8
Priority: -- → P1
Blocks: 1168885
Will be fixed by bug 1146282.
Rank: 1
Iteration: 41.2 - Jun 8 → 41.3 - Jun 29
(In reply to Tim Taubert [:ttaubert] from comment #1)
> Will be fixed by bug 1146282.

Marking as Fixed since bug 1146282 has been resolved.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
QA Contact: catalin.varga
I verified this bug using the following environment:

FF 41
Build Id:  20150716004006
OS: Win 7 x64, Ubuntu 14.04 x64, Mac Os X 10.9.5

During the verification I've noticed that on pages with mixed content the connection is presented as "Not secured" even if the unencrypted elements have been blocked. Is this expected behavior?
Flags: needinfo?(ttaubert)
(In reply to Catalin Varga [QA][:VarCat] from comment #3)
> During the verification I've noticed that on pages with mixed content the
> connection is presented as "Not secured" even if the unencrypted elements
> have been blocked. Is this expected behavior?

Yes, we show "Connection is Not Secure" for pages that load mixed display content and thus have a grey lock. As long as a page has a green lock (i.e. tries to load mixed active content but we blocked that) we will say that the connection is secure.
Flags: needinfo?(ttaubert)
(In reply to Marco Mucci [:MarcoM] from comment #2)
> Marking as Fixed since bug 1146282 has been resolved.
setting the flag accordingly
Verified fixed based on comments 3,4.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.