Firefox seems "impatient" when on dial-up.

RESOLVED EXPIRED

Status

()

Firefox
Tabbed Browser
--
major
RESOLVED EXPIRED
13 years ago
12 years ago

People

(Reporter: spamcatcherjohn, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

I'm using dial-up now with FFox. Of course I understand that dial-up is slower.
Problem is, when I am using FFox and loading in more than 1 page at a time, FFox
seems to be too willing to just give up and say that it can't find the site,
can't connect to it, or it's unavailable, or any number of excuses like that. 
But if I stop the loadin for all the tabs and load them individually, they all
load just fine.  
FFox seems to time out too easily.  I only mention this because of tabbed
browsing being a major selling point for FFox.  Seems silly to have to load each
page manually rather than selecting "Reload all Tabs" from the tab context menu.
Is there a simple way to make it wait longer before giving up?  Yes, dial-up is
slower, but I just have to deal with that.  If FFox will wait longer, it'll work
better with dial-up.


Reproducible: Always

Steps to Reproduce:
1. Start FFox
2.  Wait for my 5 homepages to load (remember, they are already cached to some
degree.)
3.  Curse when error messages start appearing.

Actual Results:  
Above mentioned errors


Expected Results:  
Loaded all pages in perfectly without problems.  Will be slow due to limited
bandwidth of dial-up, but that's OK.  Life is hard.

I have rated this as a major problem because tabbed browsing is a major selling
point of FFox.  (I mean it's a major reason why people switch from IE to FF)
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.