[Webkit-unassigned] [Bug 42048] New: Hebrew with 'charset=iso-8859-8' and 'dir=rtl' displayed incorrectly
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sun Jul 11 15:26:44 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=42048
Summary: Hebrew with 'charset=iso-8859-8' and 'dir=rtl'
displayed incorrectly
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Windows XP
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Layout and Rendering
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: ophers at gmail.com
I'm using Google Chrome to open the attached html page.
The second row in the table is rendered incorrectly in Chrome.
These browsers display the page correctly:
Firefox 3.x: OK
IE 7: OK
IE 8: OK
What steps will reproduce the problem?
1. open attached html file in IE, FF and Chrome
2. the second row in the table is rendered incorrectly in Chrome.
What is the expected result?
The second row in the table should be rendered as in IE and FF.
What happens instead?
Hebrew in the second row in the table is backwards as if Chrome is ignoring
the 'dir=rtl' attribute.
Please provide any additional information below:
RFC1556 defines 'Visual directionality' (indicated by 'charset=iso-8859-8')
as:
Visual directionality is a presentation method that displays text
according to the primary display direction only, which is left to
right. All text is viewed in the same direction which is the primary
display direction. The displaying application is not aware of the
contents direction and displays the text as if it were a uni-
directional text. ...
When an element has 'dir=rtl' attribute IE and FF treat the "primary display
direction" as being Right-To-Left. Chrome does not.
Over at Chrome issue tracker http://code.google.com/p/chromium/issues/detail?id=38197#c4 this was confirmed to also be a problem with Safari.
Comment 6 later on requested for the issue to be upstreamed.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list