Thank you for bringing up this issue. I just checked, and indeed, it's an oversight on my part. It will be fixed in the next update (which is coming this week, hopefully before the weekend!).
