You take issue with the icon. For years browsers have added a padlock to the UI when https:// is being used. Do we therefore need the 'https:// part? Do you think there should be no such icon?
In fact, I would argue that displaying a globe icon for most websites, and a padlock icon for secure websites, is an enormous boon for web security. Consider the previous situation, without icons: you are asking the user to spot the difference between 'http:// and 'https://. This is not something everyone will manage.
You don't like the abstraction because you are comfortable with what is being abstracted away. This does not mean the abstraction is not valuable. It means it is not valuable to you.
Suppose the icon for your email program has a badge on it with an unread count. I'm suggesting that 'http:// is kind of like keeping that badge there with a zero when you have no emails.
It's not redundant information, it is information on what protocol is being used. That is important information. And this information is still being displayed, the only difference is it is displayed in an alternate form of an icon. An icon representation introduced by Chromium and unfamiliar to the majority of internet users. Now the Chromium developers have to decide how to display alternate protocols, will https be represented as text or as an icon? Will other browsers use the same icon representation? Are we assuming Chromium users will only use Chromium, will this confuse users who regularly use other browsers?
To say that other bugs will just be fixed ignores the bugs caused by the unnecessarily introduced complexity.