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

481–490 of 919 posts

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

#481

Post by filmor »

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…

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

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

#482

Post by [deleted] »

dbbk wrote: post #357
drb91 wrote: post #229

Earlier quoted context omitted.

How do you verify the authority owns the content? For instance: AMP urls serve content from a different authority than the one that produces the content.

Google wants to introduce Web Packaging to solve this: https://youtu.be/pr5cIRruBsc?t=543

[deleted]

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

#483

Post by CoachRufus87 »

michaelmrose wrote: post #146
CoachRufus87 wrote: post #71

Thank you to whomever submitted this. My main annoyance is that when I want to go to a subdomain, I'll typically start typing foo.domain.com, but now the browser sets it to www.foo.domain.com. Annoying.

What browser auto inserts www? It's neither firefox or chrome.

Let me clarify: since the subdomain is hidden, I now have to munge with the URL input field to just get the full url to show up so that I can then modify the subdomain.

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

#484

Post by masswerk »

UncleMeat wrote: post #430
masswerk wrote: post #294

Earlier quoted context omitted.

A proposal for better security with domain names: The domain name system has been around for decades and it's a clever and proven system. It can – and should be – taught in school and, arguably, knowledge of it is, while not difficult to obtain, essential in our times. Additional ambiguity in this is probably not what we want. Arguably, the most sincere problems arise from mixed alphabets with Unicode domains and loo…

> Arguably, the most sincere problems arise from mixed alphabets with Unicode domains and look-alike characters/glyphs. No way. The most sincere problem is that hostnames do not enforce any binding to a real world identity that users can understand (nobody inspects certs) and that the most trustworthy component of a hostname is the second to the last section (right before ".com"). Humans tend to look at the front of…

On a higher level, all those considerations are about a single question: Is the Web about communication (then it's probably OK as it is), or about a viable business platform with an entry-level as low as it can be?

Who's without interest may throw the first stone, er, browser extension.

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

#485

Post by theyinwhy »

combatentropy wrote: post #460

Dear Google, just do syntax highlighting. Make the subdomain gray. You can even color https: green and http: red. But don't hide them. I really think syntax highlighting will accomplish the same thing for less technical users.

Grey is usually understood as greyed out: not selectable, non-functional and therefore counter-intuitive as well.

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

#486

Post by jeena »

Spivak wrote: post #436
basch wrote: 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…

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

I have many websites which I don't let Google to index, how would my users access them?

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

#487

Post by fireattack »

ehsankia wrote: post #209
fireattack wrote: post #99

I'm ok with hiding "www.", but it also hides "m." which is sometimes very confusing (I once opened a m.facebook.com link and was very puzzled why it uses the mobile site when the URl bar just shows "facebook.com").

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…

I don't get what you mean, I'm talking about opening an "m.facebook.com" link on my desktop computer Chrome. So not sure why "Show desktop version" is relevant.

>Very few sites actually use www. vs m.

Well, facebook does that.

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

#488

Post by jake_the_third »

wingworks wrote: post #468
hrez wrote: 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.

No, users expect to type what they see in the address bar, and get the same result every time.

Can we even call them address bars anymore?

And blaming website owners for working within the bounds of published standards is ridiculous and you know it.

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

#489

Post by randallsquared »

cptskippy wrote: post #441
basch wrote: 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…

What's your rationale for this? The removal of the superfluous www subdomain makes sense. It puts to actual unique site information immediately after the padlock. Most sites either redirect to it away from www when you visit them anyways. People have always said to host your site at www and redirect to it, something I have never understood nor heard a convincing argument for. I have my servers configured to redirect…

> People have always said to host your site at www and redirect to it, something I have never understood nor heard a convincing argument for.

It comes from the long-lost days when people actually ran their own servers, and would have [www,mail,ns1,ns2,intranet,chat].example.com servers. If you already have a lot of special-purpose domains, it seems weird to privilege "www" as the real example.com, so the recommendation was to redirect from it.

Post reply on HN