Sorry for the inconvenience .. In fact, I had the error fixed already but haven't merged it into production as I wanted to collected some more changes first.
Anyways, I deployed the fix today (together with the yet-to-be-announced updates) and it works as it should: