We had another report about the very same issue. It seems this bug has been around for a long while, actually, and we just missed it.
We'll fix it. Given that we are a version ahead by now on Patreon, it might not come out as a hot fix, but rather be fixed for version 0.3.9 when we release it here, hopefully next month.