Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome 69: “www.” subdomain missing from URL

bugs.chromium.org

Post reply on HN
Print view View original

431–440 of 919 posts

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

#431

Post by parliament32 »

abalone wrote: post #393

> This is a dumb change. No part of a domain should be considered "trivial". As an ISP, we often have to go to great lengths to teach users that "www.domain.com" and "domain.com" are two different domains... What ISPs teach their users anymore these days? Why the heck do we want to go back to that? Time for a modicum of historical perspective. If you care about usability this is clearly an improvement. This is part o…

What exactly is the usability improvement from hiding part of the domain name? Maybe we should be hiding ".com" because that's trivial too? Better yet, why show "google" at all if from the page it's clear you're on Google? Might as well just fullscreen the content pane and be done with it.

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

#432

Post by [deleted] »

soared wrote: post #54

Why does this matter? Users don't care and its easier to remember/understand that all websites are just "x.com" rather than sometimes being "www.x.com". If you have some server/troubleshooting/network/dev problem with it, the missing info should be moved to developer tools. This is just removing data that is useless and confusing to 99.9% of users - whats the problem?

[deleted]

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

#433

Post by EvanAnderson »

rsync wrote: post #309
cbhl wrote: post #104

Earlier quoted context omitted.

If you click into the address bar to copy/paste, the full URL will come back.

"If you click into the address bar to copy/paste, the full URL will come back." Which is also terrible behavior. Unwanted characters hidden into your paste buffer is at best unexpected and capricious behavior and at worst a source of serious, possibly catastrophic consequences (depending on what, and where, you are pasting). How soon until a doctored up paste buffer contains, by design, a newline character ? I'm sure…

Thank you for validating that I'm not the only person who hates Chrome's horrible clipboard behavior. When I highlight something and copy it to my clipboard I expect exactly what I've highlighted to be on my clipboard-- not some editorialized version of it.

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

#434

Post by hrez »

DougBTX wrote: post #407
slenk wrote: post #396

Earlier quoted context omitted.

Two prominent examples noted in the bug: https://citibank.com.sg and https://www.citibank.com.sg are different, http://www.pool.ntp.org and http://pool.ntp.org are different. Like, big companies run separate servers on the two domains. That's besides the fact where if you have www.example.www.example.com, it rewrites to example.example.com.

The first citibank url doesn’t load for me, so it is site vs not site rather than two different sites, and both those ntp urls are redirecting me to https://www.ntppool.org/en/ - perhaps there’s less substance than meets the eye to those complaints.

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?

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

#435

Post by schmichael »

abalone wrote: post #393

> This is a dumb change. No part of a domain should be considered "trivial". As an ISP, we often have to go to great lengths to teach users that "www.domain.com" and "domain.com" are two different domains... What ISPs teach their users anymore these days? Why the heck do we want to go back to that? Time for a modicum of historical perspective. If you care about usability this is clearly an improvement. This is part o…

> If you care about usability this is clearly an improvement. This is part of a long-running industry trend -- Safari does this too -- to improve the usability of the Internet and technology in general.

I am genuinely interested in knowing if this is a usability improvement. Citing "Apple does it too" is not convincing to me.

It seems to me if URLs are meaningless to you, hiding part of them is meaningless to you so why do it? It seems just as plausible that it's only unusual subdomains that confuse users ("Is foobaz.example.com the same entity as example.com?!"), so hiding common ones might only make uncommon ones more confusing.

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

#436

Post by Spivak »

basch wrote: post #424
daveFNbuck wrote: post #406

Earlier quoted context omitted.

How does hiding part of the domain make the web any easier to use?

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…

Why even bother with URL language? It should just be 'Google Search' in the bar and you can see the URL if you want.

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

#437

Post by TheKarateKid »

abalone wrote: post #393

> This is a dumb change. No part of a domain should be considered "trivial". As an ISP, we often have to go to great lengths to teach users that "www.domain.com" and "domain.com" are two different domains... What ISPs teach their users anymore these days? Why the heck do we want to go back to that? Time for a modicum of historical perspective. If you care about usability this is clearly an improvement. This is part o…

I agree. I can't remember the last time myself or anybody else actually typed "www." when going to a website.

However, Chrome should handle this intelligently like it does with localhosts vs. internet hosts. If you manually type in "http://" into the address bar (e.g "http://my-local-domain"), it will not search the usual DNS and will honor any locally configured domains you may have on your network.

This doesn't seem to be the case now with this 'www' concern, though. With slenk's example of http://www.pool.ntp.org and http://pool.ntp.org - the only way to access the second link properly is to click the link. Typing it in the address bar loads the same website as first link - so it appears Chrome is automatically adding 'www' or somehow making the request differently making the second link's page inaccessible via the address bar.

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

#438

Post by wpietri »

uberman wrote: post #169
wpietri wrote: post #139

Earlier quoted context omitted.

It's not the same issue at all, in that domains with different suffixes are controlled by different people while foo.com and www.foo.com are controlled by the same people. If you have an example of somebody who needs to serve different web content for foo.com and www.foo.com, I look forward to seeing it. But I've never seen one, and when I've seen it happen accidentally it's due to idiocy.

I realize it is an important distinction, I'm glad you do as well. Just as ftp.mysite.com is not mysite.com and mysite.com in not mysite.io and http://mysite.com is not https://mysite.com . You get the point. They are all different and important in my opinion. Any argument that hiding the "www." part makes it easier for the user is equally applicable (and wrong) to ".com"

You can keep repeating your point, but if you want to convince me, you'll have to actually address my demonstration that the two are in fact not equal in practice.

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

#439

Post by daveFNbuck »

basch wrote: post #424
daveFNbuck wrote: post #406

Earlier quoted context omitted.

How does hiding part of the domain make the web any easier to use?

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…

I think re-ordering like that would actually benefit technical users more, but it's probably too late to make such a change. I don't think we'd need that change for browsers to put the parts they consider most relevant in bold. That logic is simple enough right now.

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

#440

Post by ender7 »

slenk wrote: post #396
abalone wrote: post #393

> This is a dumb change. No part of a domain should be considered "trivial". As an ISP, we often have to go to great lengths to teach users that "www.domain.com" and "domain.com" are two different domains... What ISPs teach their users anymore these days? Why the heck do we want to go back to that? Time for a modicum of historical perspective. If you care about usability this is clearly an improvement. This is part o…

Two prominent examples noted in the bug: https://citibank.com.sg and https://www.citibank.com.sg are different, http://www.pool.ntp.org and http://pool.ntp.org are different. Like, big companies run separate servers on the two domains. That's besides the fact where if you have www.example.www.example.com, it rewrites to example.example.com.

So citibank and NTP will need to change their domain structure. That's okay: those are confusing structures.

This is a tradeoff -- continuing to support already-confusing differences is not worth the loss of the ease-of-use gain referenced in the grandparent.

Post reply on HN