Good catch! We just fixed this issue and the fix will be in version 0.11.4. Thank you very much for reporting!
