[Webkit-unassigned] [Bug 78584] New: [Encoding] Should we run text encoding detector for iframes and child frames?

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=78584

           Summary: [Encoding] Should we run text encoding detector for
                    iframes and child frames?
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
               URL: http://www.tku.ac.jp/~z-jinnai/
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Page Loading
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: yosin at chromium.org


There are garbled text in iframe/child frame even if auto text encoding detection.

Below is sample URIs for re-producing:
o http://www.tku.ac.jp/~z-jinnai/
  Main document having charset declaration ISO-2022-JP
o http://www.tku.ac.jp/~z-jinnai/06.09.13.htm
  IFrame document. No charset declaration. Encoding is Shift_JIS

Here is observation.
o When loading iframe document, TextResourceDectoder states are
  - m_source = EncodingFromParentFrame
  - m_hintEncoding = NULL
o Because of TextResouceDecorder::setHintEncoding is called with
  - hintDecoder.m_source = EncodingFromMetaTag

A comment of setHintEncoding says hint encoding should only be from auto detection.
I'm not sure why it does so.

If we set hint encoding regardless of encoding source, this page won't have garbled text.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.