Already confirmed the bug, so it is indeed unintended behavior. We’ll work on a fix for this on the next version as we couldn’t yet detect the origin of the problem.
