Hi Leo,

Thanks for the report. We're planning to address this problem during our January development sprint, and it is expected to be fixed in the 15.1 release. Sorry for the inconvenience in the meantime.

Thanks,
Josh