My guess is that this fix is probably on the list for 2.0--surely it's the kind of thing that really bothers programmers once they know about it?
But like any of us, devs only have so much time in day, and despite my great love of good documentation and early info, I'd rather have them working on the code than typing here to tell us about the code they're not working on.