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)
Tracking
()
VERIFIED
INVALID
M4
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.
Re-assinged to ftang@netscape.com and changed component to I18n.
Updated•26 years ago
|
QA Contact: 3849 → 4338
Comment 2•26 years ago
|
||
Montse, not sure who to set QA contact to.
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
Assignee | ||
Comment 4•26 years ago
|
||
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 ?) .
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.
Description
•