This happened with an earlier build. We think it has reverted to that build for some reason, or it broke again. We will do some more digging. We am glad you found the workaround. Thank you very much for finding this glitch. - GiG Dev team