I cannot edit the issue but can confirm the behavior in 5.0.3.