Closed
Bug 1462556
Opened 7 years ago
Closed 5 years ago
Mark HTTP page as insecure on address bar
Categories
(Firefox :: Address Bar, enhancement, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1562881
People
(Reporter: lolipopplus, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: parity-chrome)
since now HTTPS pages are mainstream, we are surely to address HTTP as insecure with some visual indicators.
Reporter | ||
Updated•7 years ago
|
Updated•6 years ago
|
Since 61 is already released, I think 62 should be the goal so it wouldn't be too far from Chrome.
Perhaps use the "Not Secure" text on 63, too?
Firefox can't wait too long after Chrome, otherwise it is going to be the "browser where pages are safe".
Updated•6 years ago
|
Blocks: https-everything
Reporter | ||
Comment 3•6 years ago
|
||
Chrome has this in its 68 already. I wonder when this can happen for Firefox. If Firefox falls too far, it just becomes much less competitive
Comment 4•6 years ago
|
||
I would like to see this in Firefox, too, but I doubt this statement is true. Firefox won't become "muss less competitive" because it doesn't mark HTTP pages as insecure. By the way: I already see users complain about this feature in Chrome. I still think it's the right thing to do but I don't see any relation between this feature and competitiveness, that doesn't make much sense.
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox60:
affected → ---
status-firefox61:
affected → ---
status-firefox62:
affected → ---
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•