CharCoding not retained in cached copy w/ Auto-Detect on




18 years ago
18 years ago


(Reporter: blee, Assigned: shanjian)


Windows NT

Firefox Tracking Flags

(Not tracked)





18 years ago
(Moved over from

Steps to reproduce:
1) Load a KO or CH page (e.g. URL above) in JA 10-13-08-MN6(Win32).
2) Select EUC-KR (not Auto-Detect) from CharCoding menu to display the page.
 * EUC-JP and JA Auto-Detect are left on as they were (default).
3) Click any picture/image or text link to jump to another page.
4) Click Back button to return to the home page loaded.

==> The newspaper home page is displayed in garbage again since the selected 
encoding (EUC-KR) is not retained with cached page. CharCoding reverts to EUC-JP 
on the cached copy. Happens only in JA bld, and NOT in US 10-13-08-MN6(Win32).

------- Additional Comments From 2000-10-31 15:17 -------

I don't see the problem. Is it still valide for 1030 build?

------- Additional Comments From 2000-10-31 16:16 -------

Still happens in JA 10-30-09-MN6.

------- Additional Comments From 2000-10-31 16:31 -------

This turned out to be an I18n problem. The reason why it didn't happen in US bld 
was that Auto-Detect is off as default in US bld. As soon as an Auto-Detect was 
on US 10-30-09-MN6 exhibited the same problem. Editing Summary and re-assining.

Comment 1

18 years ago
reassigning to shanjian per bobj.
Keywords: rtm
QA Contact: teruko → blee


18 years ago
Keywords: ja

Comment 2

18 years ago
According to momoi, this is the correct behavior: CharCoding info is retained in 
cached copy, but Auto-Detect takes precedence and overrides it. If this is 
correct, please resolve this as WorksForMe.
Assignee: shanjian → cata

Comment 3

18 years ago
move all cata's bug to ftang
Assignee: cata → ftang

Comment 4

18 years ago
reassign to shanjian
Assignee: ftang → shanjian

Comment 5

18 years ago
Changing QA Contact to ylong.
QA Contact: blee → ylong

Comment 6

18 years ago
Yes, this is the right behavior. Users tend to think that 
cache charset should override autodetecting result, but that 
have one problem that we do not have an easy fix yet. If user
visit some page and find that the page is not in right encoding,
he may choose an autodetector to try it again. If we let charset
in cache has high priority, this newly chosen autodetector will 
not work.
Last Resolved: 18 years ago
Resolution: --- → WONTFIX

Comment 7

18 years ago
Mark as verified. 
Also with both 6.01-ja RTM and recently trunk build, I couldn't see this 
problem on WinME-ja.
You need to log in before you can comment on or make changes to this bug.