While we are excited to see users adopt HTTPS-First Mode in future versions of Chrome, HTTP connections will still continue to be supported and Chrome will take additional steps to protect and inform users whenever they are using insecure connections. In all cases, we'll provide advance notice if we decide to move ahead with a full launch. Importantly, a "Not Secure" indicator will continue to show on sites without HTTPS support, and the experiment includes an enterprise policy in case organizations want to opt-out. We hope that this experiment will improve the discoverability of critical privacy and security information and controls provided in Page Info, such as site permissions. To try and reduce this confusion, Chrome will run an experiment in M93 that replaces the lock in the address bar with a more neutral entry point to Page Info (example below). In a recent study, we found that only 11% of participants could correctly identify the meaning of the lock icon. In particular, our research indicates that users often associate this icon with a site being trustworthy, when in fact it's only the connection that's secure.
As we approach an HTTPS-first future, we're also re-examining the lock icon that browsers typically show when a site loads over HTTPS.
0 kommentar(er)
