This issue actually existed since 1.7. I first observed this in 1.12 testing when they are back; now it is a good time to fix them.

@Generalcamo do we close all fix in next update issues?