Chrome works that way, shows https://, hides http://. It's absolutely fine. The less stuff you have to look at, the more efficient you are.
If the idea is to drop the prefix because it's redundant and useless to most, then it's same for https. All what matters to the end user is that he is on a secure connection, I think.
I'm not saying it makes perfect sense, just that I wouldn't be surprised if that's the idea behind it.