This is not a bug but intended behavior introduced in ver. 1.2.1, as noted here:
Though I’m perplexed as to why this was added: what problem does it solve?