[deleted]
Chrome 69: “www.” subdomain missing from URL
101–110 of 919 posts
Re: Chrome 69: “www.” subdomain missing from URL
#102Looks like this is intentional. To change it back go to chrome://flags/#omnibox-ui-hide-steady-state-url-scheme-and-subdomains and disable the setting.
Additionally, if this flag ever goes away, the "kFormatUrlOmitTrivialSubdomains" is the internal flag for this, it seems[1], though its description says it's "Not in kFormatUrlOmitDefaults"[2].
Back when they removed the "http:" off of URLs, I used to use a hex editor to turn the kFormatUrlOmitHTTP bit flag off every time I got a new build, so I'd get the URL formatting I wanted, but eventually lost the mental wherewithal to continue the hack every week.
[1] https://github.com/chromium/chromium/blob/3d41e77125f3de8d72...
[2] https://github.com/chromium/chromium/blob/78aae16be65e409075...
Re: Chrome 69: “www.” subdomain missing from URL
#103Re: Chrome 69: “www.” subdomain missing from URL
#104If the browser uses some technique to detect that www.domain.com is functionally identical to domain.com for a given domain, then I don't see a serious problem with this. But if they are short of that certainty, they're obscuring a critical part of the URL, and harming usability (e.g., if I want to jot down a site's URL for later use, I might get something unexpected).
If you click into the address bar to copy/paste, the full URL will come back.
Re: Chrome 69: “www.” subdomain missing from URL
#105Just updated to see it in action. Seems like a nice improvement for end users. Don't think there is any reason not to do this, other than a nostalgic desire for things to stay the same. Most sites already have a www. to . redirect in place and if you don't its a trivial change.
Why not drop the .com then as well? Most sites are on .com domains after all.
Re: Chrome 69: “www.” subdomain missing from URL
#106Why 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?
Because they are on www. and not *.
What happens when you copy and paste that URL?
Now every single website that wants to support Chrome needs to ensure that https://foo.com is always redirected to https://www.foo.com, or at least works as if it's www. It doesn't matter that most websites already do this, it's not standard, and represents Google breaking standards because they are big enough to do their own thing.
It's just one of the 1000s of papercuts that google is inflicting to keep users from switching web browser.
Re: Chrome 69: “www.” subdomain missing from URL
#107Earlier quoted context omitted.
It's about the principle. www is a valid subdomain. Browsers are supposed to be as unopinionated as possible since they are browsers , not mediators, and their job is to implement the standards of the web.
You want your browser to show unlimited popup windows too?
This is a fair point. A possible counterpoint is that one can draw a line at malware. A fairly strong argument can be made that controlling popups is an exceptional security measure that is the only way, or the most effective way, to control the spread of objectively dangerous software. It is also a matter of UI - popups could appear faster than a human could control them, so it makes sense to make popups opt-in (which they are).
No similar argument can be made about disabling "www." It is purely an opinionated decision amounting to "you don't need www" - assuming it's not a bug, of course.
Re: Chrome 69: “www.” subdomain missing from URL
#108Earlier quoted context omitted.
That's not the case. I run a server that does not respond to "www." If I enter "www.myserver.com" into the address bar, I get a DNS lookup failure, but the address bar is now showing "myserver.com." That's damn confusing, and this is an idiotic default on Chrome's part.
That seems like an edge case worth submitting a separate bug for.
It's not an edge case, it's a specific customization required to support Chrome browsers only.
Re: Chrome 69: “www.” subdomain missing from URL
#109Earlier quoted context omitted.
Firefox's behaviour is that is makes everything except the eTLD+1 grey, because that's what's normally useful for evaluating authenticity. There's no distinction made between `www` and any other subdomain.
These are all in the same origin so they can read cookies and manipulate pages.
Subdomains are in different origins; cookies have their own weird notion of security.
Re: Chrome 69: “www.” subdomain missing from URL
#110If the browser uses some technique to detect that www.domain.com is functionally identical to domain.com for a given domain, then I don't see a serious problem with this. But if they are short of that certainty, they're obscuring a critical part of the URL, and harming usability (e.g., if I want to jot down a site's URL for later use, I might get something unexpected).
That's not the case. I run a server that does not respond to "www." If I enter "www.myserver.com" into the address bar, I get a DNS lookup failure, but the address bar is now showing "myserver.com." That's damn confusing, and this is an idiotic default on Chrome's part.
Likewise, something is saying that their bank only works through www.bank.com. But the URL says bank.com. If they try to type in bank.com it doesn't work.
But hey, now we don't have to see www which has been around forever and is a surprise to no one!