4.2 Release Notes

Has this been fixed in 4.2?