Chrome developers announced the addition of a new experimental setting "chrome://flags#omnibox-default-typed-navigations-to-https" to the Chrome Canary, Dev and Beta test branches, which, when activated, will open the site using the "https://" scheme instead of "http://" by default when typing host names in the address bar. In the scheduled March 2 release of Chrome 89, this feature will be enabled by default for a small percentage of users and, unless there are unforeseen issues, the default HTTPS will be offered to everyone in the Chrome 90 release.
Recall that, despite a lot of work to promote HTTPS in browsers, when typing a domain in the address bar without specifying a protocol, βhttp://β is still used by default. To solve this problem, Firefox 83 introduced an optional "HTTPS Only" mode, in which all requests made without encryption are automatically redirected to secure page variants ("http://" is replaced by "https://"). The replacement is not limited to the address bar and also works for sites explicitly opened by "http://", as well as when loading resources inside the page. If forwarding to https:// ends with a timeout, the user is shown an error page with a button to make a request to "http://".
Source: opennet.ru