I just installed 5.2.0.0.alpha1 (Build ID: 902b28a39528b6c92602e9b521a1d0861be1caf9) and I cannot reproduce this bug there.
It would be great if someone could confirm this.
I just installed 5.2.0.0.alpha1 (Build ID: 902b28a39528b6c 92602e9b521a1d0 861be1caf9) and I cannot reproduce this bug there.
It would be great if someone could confirm this.