Greg,
I've never seen this problem being reported by another user, so ISTM
it's fair to use 'uncommon' (as in 'rarely occurring or appearing,
infrequent, occasional, unusual') to refer to it. Also, AFAIK, 'Repair
or Change' is rarely reliable.

But I agree that if we can fix this with a acceptable cost/benefit, we
should do it. If you can reproduce the issue with 2.6/3.0 (2.5 won't be
fixed anymore) and post details about it, we can argue about the
potential benefits (easy to trigger? what kind of harm does it cause?)
and compare them to the known costs (developer time, new bit of code to
maintain, etc.).

So I'm setting this to pending and will set to open/closed when we get
enough details to justify wanting to fix it or not, OK?

Thanks for reporting this and for you feedback :)