Anonymous May 10, 2016 at 16:13 #29881 We’ve just fixed the issue in the development build. A new maintenance version is expected to be published in about one week.