This is not fixed yet, at least not with version 0.46.17-alpha. I was surprised that that happened so quickly, I believe it would take much longer.
But what has been fixed with version 0.46.17-alpha is this bug report from @krst today:
Seems to be a mix-up.