Postby JS-Support @Userware » Mon Mar 14, 2016 2:54 am
Thanks for reporting this issue.
We have been able to reproduce it. It appears to happen only with IE and Edge (it works fine in Chrome, Firefox, Safari).
We expect to fix it by Q3 2016.
Regards,
JS-Support