Bug 83482

Summary:

textPath not laying out characters correctly

Product:

WebKit

Reporter:

Jake <jake>

Component:

SVG

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED WORKSFORME

Severity:

Normal

CC:

jake, sabouhallawa, zimmermann

Priority:

Version:

528+ (Nightly build)

Hardware:

OS:

Windows 7

Attachments:

Description	Flags
Test case showing character alignment issue with textPath	none
Chrome win7 output shows alignment issues	none
IE 9 output for comparison	none
Chrome win7 pdf output	none

Jake

Reported 2012-04-09 10:06:38 PDT

The <textPath> element is not laying out characters along the path correctly. Attached is a test case svg.

Attachments
Test case showing character alignment issue with textPath (9.66 KB, image/svg+xml) 2012-04-09 10:07 PDT, Jake	no flags	Details
Chrome win7 output shows alignment issues (33.90 KB, image/png) 2012-04-10 12:51 PDT, Jake	no flags	Details
IE 9 output for comparison (67.25 KB, image/png) 2012-04-10 12:51 PDT, Jake	no flags	Details
Chrome win7 pdf output (84.51 KB, application/pdf) 2012-04-10 13:01 PDT, Jake	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Jake

Comment 1 2012-04-09 10:07:28 PDT

Created attachment 136250 [details] Test case showing character alignment issue with textPath

Jake

Comment 2 2012-04-10 12:51:29 PDT

Created attachment 136517 [details] Chrome win7 output shows alignment issues

Jake

Comment 3 2012-04-10 12:51:57 PDT

Created attachment 136518 [details] IE 9 output for comparison

Jake

Comment 4 2012-04-10 13:01:36 PDT

Created attachment 136520 [details] Chrome win7 pdf output

Said Abou-Hallawa

Comment 5 2015-04-27 14:36:59 PDT

There is no much details on what was wrong with the textPath layout. The attached images are from Chrome and IE. The Chrome image did not have the proper font quality but Chrome is not using WebKit anymore. Besides the bug is no repro in Chrome anymore. Since WebKit displays the attached test case as other browsers including FireFox and Chrome itself. I am going to resolve this bug as "WORKSFORME".

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