We are sorry for that issue. We have reproduced it and we can confirm this issue. We have created a Jira bug ticket for it WEB-2157 (you can see it attached to the first post in this forum thread) and when it will be resolved you will be notified here.