I doubt that it has been fixed "in the next maintenance release".
After upgrading to 4.2.4, we are back fixing this issue again.
I doubt that it has been fixed "in the next maintenance release".
After upgrading to 4.2.4, we are back fixing this issue again.