Comment 3 for bug 495977

I'll work on trying to reproduce this.

In the meantime, you can work around it by disabling Javascript when you hit the +filebug page, which will mean that the page goes back to the old style two-step process (though that will mean that any suggested dupes are all expanded; at least it'll work).

We should also probably add a means by which users can bypass the inline version of the dupe finder if necessary, say by adding ?no-async-dupefinder=1 to the URL or something.