User-Agent: Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 Any gopher-page in a tab which is loading will continue to load if you close the tab. Furthermore, it will update the tab that is now active. It shouldn't meddle with other tabs, when it has been closed. The problem only seems related to pages using gopher but is reproducable under any gopher-page. Reproducible: Always Steps to Reproduce: 1. Open another tab 2. Go to any gopher-page, e.g. gopher://gopher.quux.org/ 3. Click a "link" on the gopher-page and QUICKLY close the tab before the new gopher-page is loaded Actual Results: The tab closes, but the gopher-resource is still loaded, now into another tab. Expected Results: The tab should just close and the gopher-request should be aborted/ignored, just like closing any other tab where a resource is loading. Note that the problem only occurs on gopher-resources (as far as I have checked) - no problem with HTTP or FTP. It seems to be reproducable of any gopher-page (if you're able to find any :)
The error only seem to happen when you enter a folder (like "Archives" or "Computers" at the given URL: gopher://gopher.quux.org/ ) - not if you access a file. For an easy test, just open this URL in a new tab, click on a folder, and quickly close the tab. At my last test it even updated a tab in another window (I had several Mozilla-windows with several tabs open).
It even seems that the resource - when interrupted (when closing the tab) - isn't loaded fully, but will only give the name of the directory/folder the user has entered.
14 years ago
I see this on LInux 2004030208
I see this on Win98 1.7 RC1. Also confirming that this is Gopher-specific (HTTP and FTP are fine).
Confirmed on x86 Linux Firefox 1.0.
Works on current trunk. Fixed sometime this month, although I'm not exactly sure when; bug 312760 seems likely, but I don't see a need to check.
The issue is still present in Bon Echo.
Bon Echo is 1.8 branch-based; please don't reopen core bugs based on it. This works in current trunk (1.9) builds. Yes, I know it's confusing that the latest alpha doesn't have fixes from a while ago, but the Firefox devs wanted a stable base to work from for Firefox 2.0, so it uses basically the same rendering engine as FF 1.5.