Comment 26 for bug 89071

I'm inclined to vote for WFM, or at least non-blocker. Google has made two significant changes since http://web.archive.org/web/20070202162244js_/tools.google.com/firefox/install.js - they now |setTimeout('addonsDown()', 3000)| instead of the previous 1000, and addonsDown() now directly sets the iframe .src to the XPI URL, instead of the previous (and uncached, so who knows what it was doing) http://tools.google.com/firefox/install2.html?theURLoftheXPI, and one or the other or both mean I can no longer reproduce the bug.

If you still want to fix it as an abstract problem, I think to reproduce you need a page equivalent to https://addons.mozilla.org/google/google_webcomments.html served with nocache headers so you don't wind up with it stuck in your cache, and another page that loads it in an iframe with an adjustable setTimeout() that changes the iframe .src, so you can find the number of milliseconds for your connection speed that will let the addons-equivalent page load and trigger the install, but then will change the iframe's src before the install code finishes checking. And then if reproducing also involves whatever install2.html used to do, I guess you'd have to ask Google what it was doing.