140170 - Charset is marked incorrectly when load a page which has different charset than parent page in a tab

Status: RESOLVED WORKSFORME

(Core :: Internationalization, defect)

Description

[Yuying Long]

Build: 04-25 BRANCH build on linux RH7.2

Steps:
1. Load any page that has a link to another page which has different charset
than in parent page. e.g. parent page is a iso-8859-1 which has a link to a
gb18030 page:
http://babel/tests/browser/HTML/ go to the last link to SimpChinese gb18030.
or in this bug report page, this link here to a UTF-8 page:
http://bugzilla.mozilla.org/attachment.cgi?id=79646&action=view

2. Highlight the link and right click mouse, select "Open link in New tab".

Result:
The page load in new tab is displayed OK. However, the charset is always marked
as iso-8859-1, no mather what auto-detect madule is.

Also manually override charset doesn't work, so if you select correct charset
(GB18030 or UTF-8), the charset is still marked as iso-8859-1, but when you
select iso-8859-1 then page will be displayed garbled, and the charset still
marked as iso-8859-1. 

Note: Not reproducible on 04-25 linux trunk build.
      Not reproducible on 04-25 branch build on windows and Macintosh.

If open the page in a new window not new tab won't see the same problem.

Don't know if it's related with bug 91305.

Comment 1

[Roy Yokoyama]

ylong: is this linux only bug?

Comment 2

[Yuying Long]

Yes, linux only.

Comment 3

[Roy Yokoyama]

assign to shanjian.

Comment 4

[Frank Tang]

shanjian is no longer working on mozilla for 2 years and these bugs are still
here. Mark them won't fix. If you want to reopen it, find a good owner first. 

Comment 5

[Travis Chase]

Mass Re-open of Frank Tangs Won't fix debacle. Spam is his responsibility not my own

Comment 6

[Travis Chase]

Mass Re-assinging Frank Tangs old bugs that he closed won't fix and had to be
re-open. Spam is his fault not my own

Comment 7

[Henri Sivonen (:hsivonen)]

We inherit charset to same-origin frames (IIRC even required by spec) and intentionally not to different-origin frames. The manually triggering the detector (bug 1648464) detects independently in each frame.