Believe it or not, this issue has yet to be resolved in Android, even though it has been over two and a half years since it was discovered. Yeah, we know it probably isn't affecting a whole lot of Android users, but still, minor glitches get fixed all the time, and this should have also been taken care of long ago.
It has been confirmed that a fix is going to come eventually, but not until the next major Android version is out. As in the next major Android release after 4.2 Jelly Bean. What took Google so long to resolve it, you ask? Well, here's what a developer had to say on the matter: "Guys, it was a matter of prioritization and resources. We don't have people to put on every requested feature and we certainly were not idle during this time. I apologize it took so long."