Hello!
Thanks for the report. I don't find that issue in the code anymore. It must have been resolved for release 1.9 or 1.10 and I forgot to log it... (1.9 will be released this weekend).
Sorry for that issue :(
