Hello, thank you for the bug report! This is indeed reproducible in version 0.11.4, but it doesn't seem to happen in version 1.0, which is coming soon, so it's most likely already fixed!
Good to know, thanks.
