Closed this issue 7 years ago · 1 comments
I have no idea how this bug slipped into 1.3.3, considering that there are tests for it!
Fixed.