Thank you for reporting this, however I was not able to reproduce this issue in our latest 3.0 Preview 2.
Could you confirm this is not happening for you in our latest preview either?
If it does, could you please describe me in more detail how to reproduce this?
3.0 - preview 2 does not have this issue. I noticed it in preview 1