Hassah!!!!
While I've yet to have the time to really put it through it's paces....the appearance is that 4.2.2 has fixed the problem. I'm not yet ready to state unequivocally that it's been fixed...but that is the appearance as of this writing.
I'm afraid, though, that I cannot offer any thanks to Apple or their drones for attending to the matter. And.....it only took them SEVEN MONTHS to do it. This is just as inexcusable as the problem itself. Especially when one piles on the fact that Apple did everything within their power to ignore the problem and to ignore and silence those of us who tried repeatedly to report it and seek a remedy. This is NOT the Apple of days past. Clearly that Apple has gone the way of the dodo.
So...while I am glad that the problem is fixed, I am NOT glad it took nearly a year for them to get around to it. That borders on negligence. and compleat apathy.
The best I can offer is....it's about F'ing time!!!
....sT
PS.... to the Apple Police who will undoubtedly read this and censor it, as they have done with every other post which does not drunkenly sing the Party song and madly wave the Party flag.......I dare you not to on this occasion. Even YOU must realise that Apple dropped this ball in a big way.