Bug 65165

Summary: WebKit does not support fractional pixel word-spacing widths
Product: WebKit Reporter: Charles Ying <charles.ying>
Component: TextAssignee: Nobody <webkit-unassigned>
Status: UNCONFIRMED    
Severity: Normal CC: joshuarbox-junk1, ohad
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Mac   
OS: OS X 10.6   
Attachments:
Description Flags
Test case
none
Additional test-case none

Charles Ying
Reported 2011-07-25 23:09:59 PDT
Created attachment 101972 [details] Test case WebKit does not support fractional pixel word-spacing widths. This is necessary for approximating TeX text layout by computing line breaks and spacing manually for optimal line width distribution. A reduction is attached showing the problem. WebKit rounds the word spacing value to the nearest pixel and uses that for text layout.
Attachments
Test case (1.04 KB, text/html)
2011-07-25 23:09 PDT, Charles Ying 		no flags
Details
Additional test-case (74 bytes, text/plain)
2012-09-17 23:28 PDT, Ohad Eder-Pressman 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Joshua Richardson
Comment 1 2011-10-18 22:02:33 PDT
I confirm this is not working as of Safari5.5.1. It actually seems to take the floor of the value, which is somewhat worse than rounding to the nearest. Not useable in the units of "em"s, and inaccurate for pixels. Firefox handles this correctly, BTW.
Ohad Eder-Pressman
Comment 2 2012-09-17 23:28:46 PDT
Created attachment 164497 [details] Additional test-case An additional testcase showing content that utilizes non-integer word-spacing, is expected to align in a uniform way but fails to do so.
Ohad Eder-Pressman
Comment 3 2012-09-17 23:33:22 PDT
I confirm this is not working on Webkit. I can confirm that fractional/non-integer word-spacing is supported on IE (I tested PC IE 9.0.8112.16421IC) and Firefox-for-Mac (I tested Mac Firefox 10.0.2). See http://ohad-etc.s3.amazonaws.com/eReader%20content%20bugs/test4/index.html for screenshots of all major browsers and how they handle this case.
Note You need to log in before you can comment on or make changes to this bug.