You can easily identify secure websites with the help of the padlock, distinguishing them from unsecured ones. This feature is currently available on Safari and many other browsers on iOS
.
I would implement it exactly as Safari does, where if a website is HTTPS the lock appears, and if a website is HTTP there is no lock.
Wouldn't it be better to highlight the lack of HTTPS when that is the case and leave the default as is. Not crowding the limited UI space with an arguably unnecessary padlock sounds desirable to me. The vast majority of websites people use are using HTTPS.
laiz Although I agree with Safari parity, I think you would be correct. With the default being secure, the UI is less cluttered most of the time. When there is an issue a broken lock can appear. We don’t need to grab the user’s attention unless there is a security risk.
ForumNinja404 I agree with this can you create a feature suggestion and merge this into it?
Do we need this padlock on a new tab without any website, or is this a bug? If so, I’m happy to file a bug.
