Comment 4 for bug 460173

@Michael - the issue is not reproducible any more. Probably behavior got changed, for the better, along the way.

I guess it should be fixed for @esscrow as well.

Please feel free to close the bug.

Thanks!

-Sandeep