3 ms·
I've noticed that if you change your user-agent to something really old and turn off JS, you can still get more "normal" looking results, complete with the opti
by userbinator 7y ago
I've noticed that if you change your user-agent to something really old and turn off JS, you can still get more "normal" looking results, complete with the option to view the cached page right there, but I'm not sure how long that will last...
Also don't forget that not too long ago, Google decided to start hiding pieces of URLs and convincing the web standards groups to make that a standard:
https://www.bleepingcomputer.com/news/google/google-chrome-hides-www-and-https-in-the-address-bar-again/ https://www.bleepingcomputer.com/news/google/google-chrome-h...
(In that article there's a very visible email address of a product manager at Google responsible for this, be sure to let her know your thoughts...)
I think that's just more proof that "web standards" aren't necessarily good for the user, especially if they're controlled by anti-user corporations. It's not unlike what's happening with open-source too: "we can do all these horrible things to oppress you, but it's open-source so you can see exactly what we do to you."
- skybrian 7y agoThat's a little different. You often don't see the full URL on a phone because the text box isn't big enough, so it gets cut off. When the browser doesn't have space to show the whole thing, displaying the most security-relevant part (the domain name) makes more sense than blindly truncating the end off it, even though doing it the dumb way is how we're used to text fields working. Designing for small screens is tricky. You can still get the whole URL easily. You could send email but it's just going to come off as badly informed, unless you show that you understand what they're trying to do and still disagree.
- userbinator 7y agoThe article talks about the desktop version specifically. A phone is a little different, I agree.