Given Chrome's dominant position (65% market share), if a blanket statement is given, it should reflect what Chrome does.
Also, for quite longer than that, if a site has any https-retrieved assets in the [Chrome] browser cache, it insists on loading https-only. This is a bit stronger than trying https first, then falling back. So only the very first visit per browser-cache-instance (profile, more or less) is penalized. This extra latency is easily absorbed/amortized.
1 comment
[ 0.33 ms ] story [ 14.6 ms ] threadIn Chrome and friends, not since April 2021.
https://blog.chromium.org/2021/03/a-safer-default-for-naviga...
Given Chrome's dominant position (65% market share), if a blanket statement is given, it should reflect what Chrome does.
Also, for quite longer than that, if a site has any https-retrieved assets in the [Chrome] browser cache, it insists on loading https-only. This is a bit stronger than trying https first, then falling back. So only the very first visit per browser-cache-instance (profile, more or less) is penalized. This extra latency is easily absorbed/amortized.