RESOLVED INVALID 52455
Display problem with SVG font
https://bugs.webkit.org/show_bug.cgi?id=52455
Summary Display problem with SVG font
Leon Brocard
Reported 2011-01-14 09:37:34 PST
Created attachment 78952 [details] Tarball with HTML, CSS and font With Chrome 9.0.597.45 (Official Build 70550) beta, Webkit 534.13. Hi there - thanks for a great pirce of software. However, I've noticed a bug. Using the font Heuristica Bold in Chrome 9.0.597.45 beta, the "o" in the font looks distorted - with a square bottom-left. However, it looks fine in the Chrome resource viewer. I've attached a tarball containing the HTML, CSS and font detailing the issue. Thanks! Leon
Attachments
Tarball with HTML, CSS and font (14.61 KB, application/x-compressed-tar)
2011-01-14 09:37 PST, Leon Brocard
no flags
Safari 15.5 differs from other browsers (1023.71 KB, image/png)
2022-07-13 04:04 PDT, Ahmad Saleem
no flags
Ahmad Saleem
Comment 1 2022-07-13 04:04:12 PDT
Created attachment 460853 [details] Safari 15.5 differs from other browsers I am not sure on expected results (since there is no distortion in the 'o' letter) but Safari 15.5 respects font and load and matches with reference image given in the test case but all other browser differs from Safari as shown in the attached screenshot. If I go by Safari output matching with reference image then it can be marked as "RESOLVED CONFIGURATION CHANGED" while as for web-compat, it is different from all browsers and show me clarified. I checked the CSS and it does not have any -webkit- prefixes etc as well. If I am testing incorrectly, please test accordingly. Thanks!
Ryosuke Niwa
Comment 2 2022-07-13 13:20:36 PDT
Looks like config changed. Thanks for testing.
Alexey Proskuryakov
Comment 3 2022-07-13 18:32:37 PDT
This reproduces exactly as reported, "o" is still distorted. However, this just seems like a problem with the font? I see the same distortion when rendering this path definition in a <path>. For context, Chrome and Firefox don't support SVG fonts, only WebKit still does.
Note You need to log in before you can comment on or make changes to this bug.