I doubt any more will be done here for 1.2.  We did address the local problem, but since it was via data, I'm removing the 1.2 tag.

I did some work on this last week. nothing pushed yet...

  --Ethan McCutchen.....Tue May 11 13:57:29 -0700 2010

I was able to reproduce this in automated tests and have since fixed it. I don't think we knew of any other place where this was happening (if so we would have fixed it manually), so I'm going to close this.

  --Ethan McCutchen.....Mon Nov 01 21:34:05 -0700 2010