This seems to be a rather old bug in our software. Not sure why it hasn't been fixed by now. Maybe our developers ran into some unforeseen complications and decided it was not worth spending more time. I'll try to ask around and see if maybe they can revisit this problem.