2 ms·
Firefox seems to always display the url after the protocol, even on mobile. I don't like the protocol omission, but I've grown to tolerate it.
by bitzun 3y ago
Firefox seems to always display the url after the protocol, even on mobile. I don't like the protocol omission, but I've grown to tolerate it.
- b112 3y agoOr mayhap, been forced to tolerate it? By UI freakazoids? (A scream goes out)Function before form, always!
- kstenerud 3y agoMeh, everything's converged on https now, unless you're loading from file (in which case you probably know already). With any other scheme, the browser is going to pop up a massive DANGER WILL ROBINSON that you have to click through. The scheme is rather pointless to display in a browser bar nowadays.
- account42 3y agoHaving a separate scheme for HTTPS was a mistake anyway. TLS should be a transport detail that doesn't change the URL at all just like DNSSEC, IPv6 and QUIC don't change the URL. The browser can still display the negotiated encryption and you need HSTS anyway to fully protect against downgrade attacks - and as older ciphers are broken even that is not going to be enough.
- IlliOnato 3y agoI agree 1000%.