[Webkit-unassigned] [Bug 14475] New: Text encoding of frames cannot be detected nor changed

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=14475

           Summary: Text encoding of frames cannot be detected nor changed
           Product: WebKit
           Version: 522+ (nightly)
          Platform: Macintosh PowerPC
               URL: http://tomyun.pe.kr/temp/safari-encoding-bug/
        OS/Version: Mac OS X 10.4
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: tomyun at gmail.com


Characters in different encodings are detected and rendered correctly when they
are in a frame which properly specify text encoding. But when the frame is
poorly structured, encoding is not detected. The worse is that one can't even
change text encoding with an explicit menu command.

I've done small test with different cases. They are contained in a main page
which specifies a default encoding in a META tag.

Frame 1: When a frame has encoded characters in a raw form, without any HTML
markups.
Frame 2: When a frame has a HTML structure, but an encoding is not specified.
Frame 3: When a frame has a HTML structure with an encoding specified properly.

In Safari 3.0.2 (522.12) and nightly build, Frame 1 and 2 shows the problem. An
attempt to change 'Text Encoding' in View menu failed. When I chose an encoding
except UTF-8, nothing happened. Choosing UTF-8 made a change in rendered text
with miserably broken characters.  Frame 3 renders correctly.

Firefox 2.0.0.3 and Camino 1.5 has no problem at all. They even automatically
detected proper encoding for Frame 1 and 2.

Internet Explorer 7 on Windows does a good job as well. It detected a proper
encoding for all frames.


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