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").
Sounds like Chrome could now be a phisher's best friend…
Which is almost worse because it seems like people have put thought into this.
It's getting likely it will have to be reverted and a loud slap in the face delivered as should be.
about.www.github.io shows as about.github.io
I'm on board with this change in general, but this is absolutely something that needs to be fixed.
Not only is that just annoying and wrong, but it could be dangerous in some situations.
Also, it doesn't just stop at one removal.
http://www.www.about.www.www.stuff.www.www.example.com
about.stuff.example.com
also = about.stuff.example.com
So stuff.www.com shows as stuff.www.com
But www.www.com shows as www.com
> How will you distinguish http://www.pool.ntp.org vs http://pool.ntp.org ?
In the above case pool.ntp.org is a decades old time service, while www.pool.ntp.org is a website describing the service.
$ ntpdate -d pool.ntp.org
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 working this way, wouldn't you just send the Desktop header whenever you get mobile and want desktop?
This is indeed what it does; I wish it did more!
Specifically, when visiting responsive pages on a phone where the mobile-viewport-size layout is just 100% broken, I’d love if “Request Desktop Site” actually set the viewport to be that of a desktop browser, and then set a low CSS/viewport zoom level to compensate. I want the dual of what happens when I set the “simulate a phone of X size” option in Chrome’s inspector!
Works in many cases, although there still are sites that break with this. I have seen sites that uses the value of window.innerWidth at load and never bother listening for changes in the width. I have seen sites that uses the presence of onTouchMove event to determine whether to use a mobile layout.
Have you tried it in the last couple months? It seems like a fairly recent change in behaviour.
>Very few sites actually use www. vs m.
Well, facebook does that.