Comment 3 for bug 1854986

Adding a note that when testing bug 1749475 on a test server, I was unable to reproduce this issue. So there's a good chance that when 1749475 is committed, it will fix this issue as well.