As it figured out, Michael had reproduced this issue with 5.1.1 so I update this bug status as confirmed for 5.1.2 and incomplete for other releases as it requires investigation.
As it figured out, Michael had reproduced this issue with 5.1.1 so I update this bug status as confirmed for 5.1.2 and incomplete for other releases as it requires investigation.