I cannot reproduce this any longer with the fix applied in rev. #10463, so I guess this has been fixed!
I cannot reproduce this any longer with the fix applied in rev. #10463, so I guess this has been fixed!