Bug 39076

Summary:

[Qt] UTF-8 characters are not displayed properly when defined with UTF-8 signature

Product:

WebKit

Reporter:

Prasad <ext-prasad.adimulam>

Component:

Text

Assignee:

QtWebKit Unassigned <webkit-qt-unassigned>

Status:

RESOLVED WORKSFORME

Severity:

Major

CC:

ap, jesus, suresh.voruganti, vincent.bradley

Priority:

Keywords:

Version:

528+ (Nightly build)

Hardware:

S60 Hardware

OS:

S60 3rd edition

Attachments:

Description	Flags
HTML file	none
CSS file	none
Image	none

Prasad

Reported 2010-05-13 10:58:20 PDT

Created attachment 55997 [details] HTML file Steps To Reproduce 1. Launch the HTML page. 2. Verify that the two lines display similar characters (each line with 5 characters). Expected Outcome: First line should be displayed similar to the second line (Each with 5 chars). Actual Outcome: First line is displayed different from second line. Behavior in different browsers: ------------------------------- Safari (Ver 4.0.5): Not Reproducible Firefox (ver 3.6.3): Not Reproducible Qt Anomaly Browser: Reproducible Note: 5th character in the first line is different to the 5th character in the second line. The 5th character in the first line is not encoded and shows a rectangular box.

Attachments
HTML file (1.48 KB, text/html) 2010-05-13 10:58 PDT, Prasad	no flags	Details
CSS file (1.13 KB, text/css) 2010-05-13 11:00 PDT, Prasad	no flags	Details
Image (1.33 KB, image/png) 2010-05-13 11:00 PDT, Prasad	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Prasad

Comment 1 2010-05-13 11:00:25 PDT

Created attachment 55998 [details] CSS file

Prasad

Comment 2 2010-05-13 11:00:39 PDT

Created attachment 55999 [details] Image

Suresh Voruganti

Comment 3 2010-09-07 13:25:30 PDT

Is this still an issue?

Pat

Comment 4 2010-11-12 08:09:08 PST

Tested on Symbian and Linux with QtTestBrowser and not reproducible. Tested with Qt 4.7 and QtWebKit trunk. The displayed results on QTTestBrowser are the same as Safari and IE and Firefox Windows and Linux).

Note You need to log in before you can comment on or make changes to this bug.