Originally submitted with a patch nearly two years ago, this appears to have languished. As far as I can tell nothing else has fixed the bug in the meantime.
Could someone with check-in rights take a look at this: I think both the problem and solution are straightforward. Cheers, John. --
