This is a known bug, and isn’t intended. Thanks for the report!