This bug is fixed in 4.3.x and later, so we're electing to not fix it in 4.2.x given other code differences between 4.2.x and 4.3.x and later.