DeletedUser16026
The update took place already. Was tested and was not reproduced.It's not fixed. I would suggest not to mark it as fixed until its actually fixed even if update soon will fix it.
Thank you all, we'll pass along the info so it can be reviewed.