Yes, I can reproduce the issue. Seems a tricky one but it was probably there from the very beginning (e.g. from the start of version 3). I will investigate and let you know.
I am glad to inform you that this issue is also fixed. Since I am preparing a major version change (3.1) this time it will be delayed a bit. I am aiming to release the new version at the end of this week. So please be patient and thank you for your detailed reporting as well. If I can reproduce the issue, we are always half way there to resolve it