This should now be fixed.
Thanks for reporting this. It looks like this was working correctly before due multiple bugs stacked together emulating the correct behavior. However, when we fixed just one of the bugs during an undefined-variable scrub last month, it made the behavior change.