Closed Bug 84704 Opened 24 years ago Closed 24 years ago

Long pages reloads endlessly if auto-detect charset set to anything but off

Categories

(Core :: Internationalization, defect)

x86
All
defect
Not set
major

Tracking

()

VERIFIED DUPLICATE of bug 87413
mozilla0.9.3

People

(Reporter: gilles+mozilla, Assigned: shanjian)

References

()

Details

(Keywords: intl, regression)

2001060720 win98 2001060707 linux Set charset auto-detect to e.g. Japanese Load URL Watch it reload and reload and reload... Set charset auto-detect to off. Page loads and stops.
Shanjian, any idea?
This is not because it is a long page. The page is very special, it is involved with 2 pages. The first one shows you "Please stand by...", and the 2nd is the real bug list. When auto-detect is set to anything and if something is detected in 2nd page, we will do a reload. However, this reload bring us the first page, and when it's time for second page, charset is set to default again. This is a very trouble some situation.
Reassign to shanjian, cc to ftang. I don't see the first page is that a separate window? It doesn't seem to be happening on 6.01.
Assignee: nhotta → shanjian
Keywords: intl
On the fact that it doesn't happen on Netscape 6.01, it began to happen on trunk a few days ago.
Adding keywords "regression mozilla0.9.2". Shanjia, could you fix this for 0.9.2? IQA, could you help identify when this has started? I think there are many pages like this, I mean showing "wait for a moment" before showing the result, so this is important.
move into moz0.9.3 .
Target Milestone: --- → mozilla0.9.3
QA Contact: andreasb → ylong
*** Bug 87413 has been marked as a duplicate of this bug. ***
From bug 87413: URL http://www.netscape.fr/ also displays this problem. (I also see it on long Bugzilla BugLists) adding nsBranch Keyword from that bug.
Keywords: nsBranch
Also from bug 87413 > ------- Additional Comments From Katsuhiko Momoi 2001-06-23 04:04 ------- > Frank, this problem does not occur with 5/18 build > even wit the JPN auto-detection on. > The next build I have is from 5/22 and there the problem > occurs. So loof for a change between these dates.
*** This bug has been marked as a duplicate of 87413 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified as dup.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.