NEW 26737
Two SVG text tests fail locally
https://bugs.webkit.org/show_bug.cgi?id=26737
Summary Two SVG text tests fail locally
Eric Seidel (no email)
Reported 2009-06-25 15:48:52 PDT
Two SVG text tests fail locally svg/W3C-SVG-1.1/text-fonts-01-t.svg svg/text/text-fonts-01-t.svg I assume that it's due to font fallback. The diff: - RenderSVGText {text} at (20,240) size 286x27 contains 1 chunk(s) - RenderSVGInlineText {#text} at (0,-20) size 286x27 + RenderSVGText {text} at (20,240) size 286x24 contains 1 chunk(s) + RenderSVGInlineText {#text} at (0,-19) size 286x24 chunk 1 text run 1 at (20.00,240.00) startOffset 0 endOffset 19 width 286.00: "A mono (iW) face \x{753B}\x{50CF}" The offending SVG snippet: <text font-family="'Lucida Console', 'Courier New', Courier, Monaco, 'MS Gothic', Osaka-Mono, monospace" x="20" y="240">A mono (iW) face &#30011;&#20687;</text> As far as I can tell my font list is: Lucida Console: NO Courier New: YES Courier: YES Monaco: YES MS Gothic: YES Osaka-Mono: NO (but I do have Osaka, "Regular" and "Regular-Mono") As to the individual characters in that test, I'm not sure which fonts they are present in or not. Anyone know what assortment of fonts could be causing the problems here? And/or why the buildbots aren't seeing problems? This is a standard Google Mac Desktop. I also have MS Office 2008 installed (which is probably the problem).
Attachments
Eric Seidel (no email)
Comment 1 2009-06-25 17:16:10 PDT
I tried disabling MS Gothic, MS PGothic and Osaka and was not able to get the test to pass.
Eric Seidel (no email)
Comment 2 2009-06-25 17:20:42 PDT
Oh! Turns out that I do have Lucida Console. Disabling that font makes the tests pass on my system.
Ahmad Saleem
Comment 3 2023-09-16 15:25:08 PDT
We do have some specific handling for 'Lucida Console' throughout our code when I search across using 'searchfox.org' with keyword 'Lucida'. I didn't try to run these tests locally to see, if we hit this issue now or not but I'll CC some Text experts (i.e., Myles) to get his input.
Note You need to log in before you can comment on or make changes to this bug.