Closed Bug 94281 Opened 24 years ago Closed 24 years ago

a child win. does NOT inherit the encoding of the parent win.

Categories

(Core :: Internationalization, defect)

defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 70507

People

(Reporter: jshin1987, Assigned: tetsuroy)

References

()

Details

(Keywords: intl)

When no encoding(MIME charset) is speicified either in meta tag or by http header, a child window launched from the parent window does NOT inherit the encoding of the parent window. Instead, it shows up in ISO 8859-1 no matter what encoding is selected by users in the parent window. This is especially troublesome for a chromless window (or any window without the 'view-character encoding menu by which a user can change the encoding). * How to reproduce 1. Go to the URL above 2. If you can see Korean Hangul, the encoding of the page is detected correctly so that you can go to step 4. 3. In View-Character Coding menu, select Korean(EUC-KR) 4. Click either of the two links in the page 5. A new window will pop up, but the encoding used is NOT EUC-KR (the encoding of the parent window) BUT ISO 8859-1. * Expected result: In step 5 above, a new child window should come up in the encoding of the parent window (EUC-KR). * the version tested : 2001-08-07-03 and some earlier builds including M 0.9.3, 0.9.2 * Related bug : bug 70830
Changed QA contact to ylong@netscape.com.
Keywords: intl
QA Contact: andreasb → ylong
I think this is a duplicate of bug 70507. I should have looked it up before filing this bug. I'm marking this as a duplicate of 70507. *** This bug has been marked as a duplicate of 70507 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Mark as dup, please re-open if disagree.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.