Hey Percarus, version 1.5.0 just went live and we have patched a fix for this issue. Thanks for letting us know about this :)
