Live data from Hacker News

Chrome 69: “www.” subdomain missing from URL

bugs.chromium.org

911–919 of 919 posts

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

#911
post #481
post #424

Earlier quoted context omitted.

if anything, it should be time to declare that its a bit insane to expect lay people to be able to read from right to left and left to right concurrently, and understand all the delimiting punctuation correctly, along with unicode. its time to restructure url rendering to be right to left, and combine delimiters. dashes, periods, slashes, and subdomains and hundreds of tlds have made it too confusing. https://www.goo…

And how would the client distinguish the part that goes to DNS from the HTTP path?

double punctuation?

https://com/google/www//maps/hawaii

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

#912

Earlier quoted context omitted.

Its weird too because chrome invented to UX when closing lots of tabs not to reflow the browser UI but keep placing their close X under the mouse until you move away. So its like they understood this once and have forgotten.

Have you used the latest Chrome with the redesign? The tab's X no longer has any hover effects, or doesn't seem to. After the last few days of wondering about this, I see now that hovering over the X makes is ~5% darker.

Oh yeh I looked at the X on the current tab and didn't agree. The close X on background tabs hover is basically indistinguishable.

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

#913

Earlier quoted context omitted.

Because the second level domain is far more important than the subdomain. The second level. www.example.com and example.com usually have the same contents, but are always controlled by the same group.

It's not true that the second level and third level are always controlled by the same group (most of .uk for example). You can put an SOA record anywhere.

Are they not respecting the public suffix list?

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

#916

Earlier quoted context omitted.

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…

ugh!!!!! this is killing me

Fixed in a week (v69.0.3497.92)! Nice one Chrome

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

#917

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…

>there's a difference between "www.example.com" and "example.com" Can you link to a site where these two are different?

for ages, my former high school's website did not respond to requests that omitted the www. subdomain :/

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

#918
post #781

Most comments assume that this is for solving user confusion, or security, or building a better URL scheme, et al. It's not, that is all smokescreen. As ivs wrote[1] They are going to hide amp subdomain, so you don't know if you're looking at AMP or the actual destination. And then suddenly the whole world funnels through AMP. And for that reason, it won't be reversed until people call them for what they are actually…

AMP pages are served through google.com, though? It's one of the big problems with them.

Not always. Sometimes Google results have taken me to websites like "amp.reddit.com" on mobile.

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

#919
post #434

Earlier quoted context omitted.

user1 - https://citibank.com.sg doesn't work for me user2 - it's fine, here is a screenshot of it working (while showing "beautified" https://www.citibank.com.sg ) how is that not confusing?

I think it's more on the website owners to fix their sites, users expect domain.com to be the same/auto-redirected to www.domain.com or vice versa. I think it's a good thing what Chrome is doing, it will push website owners to correctly set up their domain redirects and in the end, lessen end-user confusion.

Coming back to this a couple of weeks later, they appear to have changed their site, and https://citibank.com.sg now redirects to https://www.citibank.com.sg/
Post reply on HN