it happened in v19, maybe v18 too, not sure
what i am sure about though is that in sub-versions the bug gets fixed then re-appears outta nowhere

Marking invalid as reproduction of the conditions showed bug did not occur.