Font/text rendering issue on online skia debugger
5 views
Skip to first unread message
Kiara Patani
10:14 AM (5 hours ago) 10:14 AM
to skia-discuss
Hi team,
I am trying to load skp generated using --enable-gpu-benchmarking --no-sandbox flags on chromium 142 version on online skia debugger. I found that no text/font is being rendered on the debugger. Later to debug this issue , I checked with previous versions of chromium and found that until chromium 134 we are able to see the fonts properly but when we check on chromium 136 , the fonts are missing. So maybe the issue is introduced from chromium 136 itself. Attaching the screenshot for reference. Is there any major change from skia chrome/m134 to chrome/m136 which related to fonts due to which we can't see the fonts on the debugger properly ?
skp generated with chromium 136/142-
I am trying to load skp generated using --enable-gpu-benchmarking --no-sandbox flags on chromium 142 version on online skia debugger. I found that no text/font is being rendered on the debugger. Later to debug this issue , I checked with previous versions of chromium and found that until chromium 134 we are able to see the fonts properly but when we check on chromium 136 , the fonts are missing. So maybe the issue is introduced from chromium 136 itself. Attaching the screenshot for reference. Is there any major change from skia chrome/m134 to chrome/m136 which related to fonts due to which we can't see the fonts on the debugger properly ?
skp generated with chromium 136/142-
skp generated with chromium 134-
bungeman
10:52 AM (4 hours ago) 10:52 AM
to skia-discuss
From the timeline, this is almost certainly due to Chromium moving from FreeType to Fontations. When deserializing an SkTypeface in SkTypeface::MakeDeserialize the matching typeface factory must be registered. However, it appears we don't have a Fontations (which is Rust) into wasm build? Looks like there is a similar issue opened at https://issues.skia.org/issues/397818456 .
Reply all
Reply to author
Forward
0 new messages