That's fixed in the latest update :)
It's still happening on my end.
Are you sure you're running 0.19.7a, and not 0.19.7?
