That's definitely not intentional so thanks for the report, you actually hit quite a rare edge case -- it's fixed now!
