Can the QA verify whether this problem does or does not exists in 4.2?
This was pushed twice, closing.