Sorry about this. It’s fixed in the latest version (16.7.78).
It was a regression bug related to this enhancement: