Closed Bug 4032 Opened 26 years ago Closed 26 years ago

Changing charset causes app to continually connect to server

Categories

(Core :: Internationalization, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: cpratt, Assigned: ftang)

Details

Load any page on the Web, and once it's finished loading, change the character set to something else (say, Shift_JIS). When you do this in Nav 4.51, the page is reloaded from the cache and displayed using the newly selected charset. When you do this in seamonkey, the app contacts the server and (apparently) never stops doing so - every page I try, it keeps contacting the server indefinitely. This behavior was seen on Windows NT.
Assignee: don → ftang
Component: XPApps → Internationalization
Re-assinged to ftang@netscape.com and changed component to I18n.
QA Contact: 3849 → 4338
Montse, not sure who to set QA contact to.
QA Contact: 4338 → 3851
Target Milestone: M4
asssigning QA contact to teruko and adding M4 as TFV
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
This is invalid. The encoding menu have not been implemented yet. Currently switching the menu do *NOTHING*. No reload, no load from cache, no conact to server (the N sign does not spin, right ?) .
Status: RESOLVED → VERIFIED
Although I take exception with the 'invalid' resolution (this was a problem until very recently), it now works for me using the April 5 99 build.
You need to log in before you can comment on or make changes to this bug.