Bug when browsing multiple pages on Mozilla 1.7.6

RESOLVED EXPIRED

Status

--
major
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: brkamikaze, Unassigned)

Tracking

1.7 Branch
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 2.0.40607)
Build Identifier: 

Whenever you brouse on Mozilla using tabs or mutiple windows, Mozilla mess up 
with the file servers and almost always get "404" errors. For example, when I 
am browsing "http://gmail.google.com" and try to browse any other page on any 
other browser window or tab. For 
example, "http://www.pdj.com.br/forum/login.php" (This page is in Brazillian 
Portuguese), Mozilla comes up with a Google custom error page saying 
that "forum/login.php" was not found on this server.

Reproducible: Sometimes

Steps to Reproduce:
1.Open an webpage on one tab.
2.Open any other webpage outside the server of the first tab.
3.Very rarely you will not get the described results.

Actual Results:  
Mozill messed up with servers and looked for the second's server file on the 
first one.

Expected Results:  
The software should have opened each page without trouble, even when using 100 
tabs.

I was using the Modern Theme.

Comment 1

14 years ago
Which version of Mozilla do you use? Do you have any extensions installed?
(Reporter)

Comment 2

14 years ago
I use Mozilla 1.7.6 on a brand new setup.

Comment 3

14 years ago
Cannot reproduce. For me, everything works as expected.
(Reporter)

Comment 4

14 years ago
It happens with me also when I use Firefox even unthemed.
I am using Windows XP without Service Packs, and I am at school.

It also happens sometimes even without tabbed browsing. I think it is a bug 
with Mozilla's searching system, where I use Google.

Updated

14 years ago
Version: unspecified → 1.7 Branch
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: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.