Fascinatingly, I myself reported this behaviour in 2015. It was fixed back then ...
but now it looks like it has crept in again.