Comment 4 for bug 1933512

Unless this has already been fixed recently, this is still a valid bug and I see no reason for it to be marked incomplete and expired. I'm setting it back to New to be re-evaluated.

I don't have access to the environment where this occurred anymore, but I may be able to respond questions if any, and eventually set up a new env to replicate the problem if you can't.