This bug does not exist in Mir 0.7, because the fix was released in the 0.6 series before 0.7 branched from it. However a separate fix exists in development-branch so it's still not "Fix Released" for 0.8 just yet.
This bug does not exist in Mir 0.7, because the fix was released in the 0.6 series before 0.7 branched from it. However a separate fix exists in development-branch so it's still not "Fix Released" for 0.8 just yet.