Comment by boomlinde

I don't see the issue with showing both an URL and a tokenized representation, outside Google's seeming motive to "kill the URL". In both versions, information that would be immediately available in the URL is potentially left out, which can't possibly help prevent phishing unless Google goes out of their way to actually verify that websites are what they say they are.

It's also hard to trust Google engineering to get something like this right after the Chrome "trivial subdomain" stripping debacle(https://bugs.chromium.org/p/chromium/issues/detail?id=881694).