Chrome 69: “www.” subdomain missing from URL

Re:Chrome 69: “www.” subdomain missing from URL by austincummings on Thursday September 06, 2018 @02:05PM (#17928087)

Looks 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.

[ Parent | on HN ]

Re:Chrome 69: “www.” subdomain missing from URL by chch on Thursday September 06, 2018 @02:34PM (#17928398)

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...

[ Parent | on HN ]

Re:Chrome 69: “www.” subdomain missing from URL by exikyut on Thursday September 06, 2018 @10:46PM (#17931517)

I have wanted to figure out for ages how to compute the location of these types of flags/vars in binary files.

Incidentally I want to figure out how to do this on Linux.

I presume I need debug symbol files, which I can download easily.

How would I do this?

[ Parent | on HN ]

Re:Chrome 69: “www.” subdomain missing from URL by userbinator on Thursday September 06, 2018 @10:45PM (#17931512)

but eventually lost the mental wherewithal to continue the hack every week.

That's when you automate it as part of your "set up my environment exactly the way I like it" scripts ;-)

[ Parent | on HN ]

Re:Chrome 69: “www.” subdomain missing from URL by keeganjw on Thursday September 06, 2018 @02:20PM (#17928246)

Thanks! This worked great for me and it brought back the https:// part as well.

[ Parent | on HN ]

Re:Chrome 69: “www.” subdomain missing from URL by pishpash on Thursday September 06, 2018 @02:31PM (#17928352)

Until a few releases down the line and it is decided for you that the flag should be removed.

[ Parent | on HN ]

Re:Chrome 69: “www.” subdomain missing from URL by rocky1138 on Thursday September 06, 2018 @03:03PM (#17928689)

This is the problem. Better to just switch to Firefox now and be done with it. Hopefully it'll send a message.

[ Parent | on HN ]

Re:Chrome 69: “www.” subdomain missing from URL by mindcrime on Thursday September 06, 2018 @04:47PM (#17929423)

Until Firefox leadership decide to make the same change "because that's what Chrome does". Sadly, over the history of Firefox (and before that, Mozilla/Seamonkey) the leadership there has always been WAY too obsessed with following IE and/or Chrome rather than just building the best browser and taking some chances.

Seriously, trawl through Bugzilla sometime and look how many bugs are closed with the the justification being some variation of "That's how IE does it" or "IE doesn't support that", etc. And then substitute "Chrome" for "IE" later in history once Chrome took over the universe.

[ Parent | on HN ]

Re:Chrome 69: “www.” subdomain missing from URL by int_19h on Thursday September 06, 2018 @05:29PM (#17929720)

Luckily we still have Vivaldi, Otter, Falkon etc.

[ Parent | on HN ]

Re:Chrome 69: “www.” subdomain missing from URL by Already__Taken on Friday September 07, 2018 @05:17AM (#17932892)

Hopefully an upside to user tracking means using this flag is kind of voting on the behaviour. If they're listening.

[ Parent | on HN ]