If you have issues with google hiding the www-prefix - can you give a reasonable explanation what it means that some webpages start with www. and others don't? (an explanation that makes sense for a user, not one of technicalities in the implementation)
Do you know how they decide whether or not to hide or add it? Flaws in this heuristic would be what's relevant to users - when, if ever, does it break things?
-
-
I don't know, but I've read it causes some weirdnesses (e.g. removing www not as the leftmost label). I think these are mere bugs and yeah, it probably would make sense to have the exact behavior properly defined.
-
Somehow it seems to avoid dropping the www on sites where the non-www doesn't work, and to add the www on sites that need it if you omit protocol, but not if you include protocol.
-
I'm not sure what happens on sites where both www and non-www exist and are different.
End of conversation
New conversation -
-
-
There is a list if trivial sub domains (such as www and m) they Chrome decided to hide. There is a flag to turn it off too. It's a good move from Chrome to have it enabled by default.
-
See followup. That's not a complete answer and doesn't address the interesting parts.https://twitter.com/RichFelker/status/1038091260727316480 …
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.