Closed
Bug 3921
Opened 26 years ago
Closed 25 years ago
Charset Handling- Problem displaying proper document charset in frame element
Categories
(Core :: Internationalization, defect, P2)
Core
Internationalization
Tracking
()
VERIFIED
FIXED
M7
People
(Reporter: blee, Assigned: ftang)
References
()
Details
(Whiteboard: Have temp fix in local tree, wait branch open to check in.)
To see this, try above URL in Mozilla M3 (reloading required).
==> JA char's aren't displayed correctly due to improper charset (specified in
the doc's meta tag) handling of the browser.
When each frame is opened individually, JA text shows up properly.
Observed in 3/17 Mac bld with latin 1, sjis and euc-jp frame element pages.
Group: netscapeconfidential?
Priority: P3 → P2
Target Milestone: M4
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
OS: Mac System 8.5 → All
Hardware: Macintosh → All
Assignee | ||
Comment 1•26 years ago
|
||
This is the place that our META tag hack does not work. It should work once
RickG put the real meta tag code in place.
Add RickG in CC list.Mark platform to all and OS to all.
Comment 2•26 years ago
|
||
Why is this bug marked "Netscape Confidential"?
Assignee | ||
Updated•26 years ago
|
Group: netscapeconfidential?
Assignee | ||
Comment 3•26 years ago
|
||
change to not confidential...
Assignee | ||
Updated•26 years ago
|
Target Milestone: M4 → M5
Assignee | ||
Comment 4•26 years ago
|
||
This is depend on the META tag work to be done (rickg). Mark it as M5
Assignee | ||
Updated•25 years ago
|
Target Milestone: M5 → M6
Assignee | ||
Comment 6•25 years ago
|
||
Change to M6. Cannot make it since webshellproxy and observer in nsDTDUtils.cpp
are not ready yet.
Assignee | ||
Updated•25 years ago
|
Summary: Problem displaying proper document charset in frame element → Charset Handling- Problem displaying proper document charset in frame element
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 7•25 years ago
|
||
Meta charset observeration is check in . This should be fixed. Please verify
against build after 5/19
Updated•25 years ago
|
Status: RESOLVED → REOPENED
Comment 8•25 years ago
|
||
Since Meta-charset does not work in 5-24-10 build, I need to reopen this.
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → ASSIGNED
Whiteboard: Depends upon rickg,neeti,harishd,nisheeth work for Meta → Have temp fix in local tree, wait branch open to check in.
Assignee | ||
Comment 9•25 years ago
|
||
Will check in tonight to both branch and tip
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Assignee | ||
Comment 10•25 years ago
|
||
fix and check in w/ 6740
Updated•25 years ago
|
Status: RESOLVED → REOPENED
Comment 11•25 years ago
|
||
crashes on Mac with build 1999052516
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → ASSIGNED
Target Milestone: M6 → M7
Assignee | ||
Comment 12•25 years ago
|
||
change to m7
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Assignee | ||
Comment 13•25 years ago
|
||
The problem is nsWebShell ReloadDocument and StopLoadingDocument reent libnet
and it trash some object on the stack. It seems only have problem if the first
block we receive have the whole META tag. (in other word, if we call the
ReloadDocument in the first block). I currently work around by don't call
StopLoadingDocument in nsMetaCharsetObserver.cpp and use new a implementation of
ReloadDocument which use RefreshURL to work aroud the problem so it won't crash
now. I will open a new bug against nisheeth about the StopLoadingDocument
problem
Reporter | ||
Comment 14•25 years ago
|
||
Verified fixed in 6/16 Mac and Win 32 blds.
You need to log in
before you can comment on or make changes to this bug.
Description
•