Same bug in 4.22.1 Its an easy workaround sure, but I feel it should still be fixed as it is unexpected behaviour.