Closed Bug 205565 Opened 21 years ago Closed 19 years ago

Mozilla 1.4a and later causes PHPOpenChat to restart "output frame" from the beginning every second.

Categories

(Core :: Networking: HTTP, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: pavelp, Assigned: darin.moz)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030512
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030512

I use the online chat room based on PHPOpenChat. The chat page consists of 3
frames, one of them ("output") displaying chat messages from all participants.
If I use mozilla 1.4a or later, the output frame restarts itself, redisplaying
all messages the server has in its log, about every couple of seconds. Works
fine with IE or Mozilla 1.3 and earlier. Looks like the HTTP connection for this
frame is reset by mozilla all the time, so server re-transmits the data.

Reproducible: Always

Steps to Reproduce:
1. Go to http://chat.voivodfan.com/chat URL using any Mozilla build 1.4a or later
2. Register and login.

Actual Results:  
See the "output" frame scrolling repeatedly and indefinitely.

Expected Results:  
Should see the chat log once, and only new messages afterwards.
Does not happen in 1.4RC1. Probably fixed.
I cannot confirm this bug, but the page do not load completely. It seems to be a
loop in loading some frames.
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
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.