No. If the bug exists in 1.6.0, it exists in 1.6.0. =)

Reply via email to