153036 - frames with multiple character encodings fail to render properly

Status: VERIFIED INVALID

(Core :: Internationalization, defect)

Description

[moof]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.0.0) Gecko/20020606
BuildID:    20020606

In the (non-worksafe) URL cited, the main frame has
  <meta http-equiv="Content-Type" content="text/html; 
    charset=Shift_JIS">
but the child frame has
  <meta http-equiv="Content-Type" content="text/html;
    charset=iso-2022-jp">

It gets the encoding of the parent frame right, but just spews unreadable
(presumably JIS-encoded) crap for the child.


Reproducible: Always
Steps to Reproduce:
Create a webpage that has one encoding in one frame (or the parent), and a
different encoding in another frame.

Actual Results:  The parent frame will render correctly, the child frame will not.

Expected Results:  It should have paid attention to the content= charset= bits
in the child frame.

My apologies for the bizarro/nonworksafe URL cited, but it was the easiest
example I could find.

Whether it's actually legal for frames to have multiple character sets is
another matter entirely.

Comment 1

[Jaagup Irve]

> but the child frame has
> <meta http-equiv="Content-Type" content="text/html;
> charset=iso-2022-jp">

The child frame also uses Shift_JIS and therefore Mozilla shows garbage as it is
told to in this meta tag. (Switch character coding to Shift_JIS to see page
properly.)

Evangelism or Invalid

Comment 2

[moof]

Ugh. You're correct. What confused me was when I did 'View Page Source' and then
View -> Character Coding -> ISO-2022, the page came up blank - so I assumed that
it was some other rendering thing. Turns out it's just a View Page Source bug,
for which I'll create a new bug.

Comment 3

[Yuying Long]

Mark as verified, charset and rendering works fine. - I changed the child frame
encoding as iso-2022-jp and keep parent page as shift-jis, the page loads properly.