Live data from Hacker News

Chrome 69: “www.” subdomain missing from URL

bugs.chromium.org

381–390 of 919 posts

Re: Chrome 69: “www.” subdomain missing from URL

#381

Safari already hides "www.". In fact it hides everything except the root-level domain, e.g. " https://www.google.com/about/" shows just "[lock] google.com". Firefox and Opera show the full domain but gray out everything in the entire URL except the root-level domain, so "www." is gray. Just saying, de-emphasizing and hiding parts of the URL is clearly a trend. This isn't just a Google thing.

It's a setting. Settings / Advanced / Show full website address to show the www.

Re: Chrome 69: “www.” subdomain missing from URL

#382

Earlier quoted context omitted.

> The UX of moving what I'm looking at instantly under click is very unpleasant too, Could you expand on this? What are you referring to?

I don't know if it's the same thing, but I'll bite: it's absolutely maddening to edit or select part of a URL. Click in the address bar and the entire address is selected, then you click on any part of it to either select a part or to place your cursor in order to add to it, after which Chrome appears to first shift the entire URL to the right in order to show the protocol, then it places the cursor within the shifte…

Yes, it's this, and it's an absolutely infuriating change.

Re: Chrome 69: “www.” subdomain missing from URL

#383
post #333

Earlier quoted context omitted.

My bet is this decision is driven somewhere by marketing morons who want 'www.google' (presumably a domain that will at some point exist, the TLD already does) to render as simply 'google'

Technically there's no reason why a TLD can't have an A record. If they own "google." they can point it to whatever address and serve whatever they want.

Until recently, http://ai did exactly this. They also had MX records, so n@ai was a valid email address.

Re: Chrome 69: “www.” subdomain missing from URL

#384
If only we had something other than the subdomain to indicate what protocol we want to use to access the host in question. Like maybe some kind of... port number and/or protocol prefix.

"www." is useless. Eliminating it wouldn't be a bad thing.

"m." for mobile sites is extremely archaic. Sites should work on mobile without special subdomains.

If you issue subdomains to strangers on your root domain, the URL bar showing the subdomain shouldn't be your "security model."

The root domain is the root authority behind the site in question. Chrome showing users that information in a clear and concise way isn't "subverting the domain name system".

Safari has been doing this for a long time, and Chrome/Chromium have settings/flags that allow you to turn this behavior off. The amount of crying over this change is ridiculous in my opinion. As long as they keep this configurable (in fact, they should add a UI config for it) I see no problem here.

Re: Chrome 69: “www.” subdomain missing from URL

#385

Safari already hides "www.". In fact it hides everything except the root-level domain, e.g. " https://www.google.com/about/" shows just "[lock] google.com". Firefox and Opera show the full domain but gray out everything in the entire URL except the root-level domain, so "www." is gray. Just saying, de-emphasizing and hiding parts of the URL is clearly a trend. This isn't just a Google thing.

this is actually the main reason I cannot use Safari. It always boggled my mind that they made this decision. For power users, they never look at the url unless they want information from it, in which case the `www` is valuable. For low tech users, it can lead to straight up incomprehensible issues, like sites not rendering properly (think of a `m.*`). The UI gains are so small, that part of the screen is never reall…

You know it’s a setting, right?

Re: Chrome 69: “www.” subdomain missing from URL

#386

Earlier quoted context omitted.

What you may be surprised to learn is that Chrome isn't just stripping "www." from the beginning of the subdomain. "subdomain.www.domain.com" displays as "subdomain.domain.com"

Isn't this a security risk? What if someone malicious takes control of the www.com domain?

The www.com might not be easy to get, but there is probably a www name at another important TLD that can be purchased. And if you own that domain you can easily get SSL certificates too.

Sounds like Chrome could now be a phisher's best friend…

Re: Chrome 69: “www.” subdomain missing from URL

#387

Earlier quoted context omitted.

When you copy and paste, it has the whole URL - just like when you copy and paste now it will include http(s)://

What if you visually copy and paste? Parent is right.

One more reason to set up a redirect from or to www.

Re: Chrome 69: “www.” subdomain missing from URL

#388
post #295

Earlier quoted context omitted.

Facebook aside, don't the majority of sites show you mobile version by looking at headers. Isn't that the whole reason the "Show desktop version" feature even exists in Chrome, to send the desktop header? Very few sites actually use www. vs m. Clearly, in those cases, people aren't "confused" by the fact that they are seeing a mobile version on www., so other than the fact that you're used to Facebook specifically wo…

> Isn't that the whole reason the "Show desktop version" feature even exists in Chrome, to send the desktop header? This is indeed what it does; I wish it did more! Specifically, when visiting responsive pages on a phone where the mobile-viewport-size layout is just 100% broken, I’d love if “Request Desktop Site” actually set the viewport to be that of a desktop browser, and then set a low CSS/viewport zoom level to…

I'm pretty sure Chrome's "request desktop site" option does change the viewport size. Or if it's doing something else, it has the same effect.

Have you tried it in the last couple months? It seems like a fairly recent change in behaviour.

Re: Chrome 69: “www.” subdomain missing from URL

#389

Considering a subdomain "trivial" is ridiculous... there's a difference between "www.example.com" and "example.com". Not only can they serve different sites, they can even have different DNS records! It seems that "m." is also considered a trivial subdomain. So when a user clicks a link to a "m.facebook.com" uri, they'll be confused why FB looks different when the browser reports it's on "facebook.com". I sincerely h…

This is certainly subverting the domain name system. I can't see the value or gain in security by this. (If you want to put focus on the domain, then display the host-part with less contrast, i.e. grey, but don't hide any potentially vital information. Otherwise, put out a RFC, defining "www" as a substitute for "*", or a zero-value atom, in order to guarantee consistent behavior.) Edit: There are also legal concerns…

The reason why Google is doing this is because they are slowly trying to do away with URLs, as direct traffic is probably their greatest untapped segment.

Google is trying to get users to go through their doorway pages, which is exactly the kind of thing for which they penalize publishers.

Pay attention to when you enter direct addresses, let's say from a device/media subscription authorization page. The autosuggestion feature will often recommend Google searches, disguised as URLs, instead of helping you complete the very obvious URL.

If they help you get to the site directly, the opportunity to acquire your page views diminishes.

These behaviors are hostile toward users. I'd like to see further in their playbook to depreciate the URL as we know it.

Re: Chrome 69: “www.” subdomain missing from URL

#390

Safari already hides "www.". In fact it hides everything except the root-level domain, e.g. " https://www.google.com/about/" shows just "[lock] google.com". Firefox and Opera show the full domain but gray out everything in the entire URL except the root-level domain, so "www." is gray. Just saying, de-emphasizing and hiding parts of the URL is clearly a trend. This isn't just a Google thing.

Safari does hide www, but it's a default setting that can be changed by checking [0]

  Preferences > Advanced > Show full website address
[0] https://imgur.com/a/3VMo5zH

EDIT: Formatting. Add missing article. Change linked image.

Post reply on HN