Bug 255216

Summary: [GTK] Paragraph and heading text not being rendered
Product: WebKit Reporter: Abrar Ahmed <abrarsl2002>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: bfulgham, bugs-noreply, mcatanzaro, simon.fraser, zalan
Priority: P2    
Version: Other   
Hardware: PC   
OS: Linux   
Attachments:
Description Flags
Screenshot of the bug
none
screenshot on macOS
none
Text is rendered when zoomed in none

Abrar Ahmed
Reported 2023-04-10 00:13:39 PDT
Created attachment 465826 [details] Screenshot of the bug Can be reproduced at this site: https://gtk-rs.org/gtk4-rs/stable/latest/book/list_widgets.html
Attachments
Screenshot of the bug (139.45 KB, image/png)
2023-04-10 00:13 PDT, Abrar Ahmed 		no flags
Details
screenshot on macOS (346.82 KB, image/png)
2023-04-10 08:22 PDT, zalan 		no flags
Details
Text is rendered when zoomed in (173.49 KB, image/png)
2023-04-11 06:38 PDT, Abrar Ahmed 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
zalan
Comment 1 2023-04-10 07:18:14 PDT
Thank you for filling this bug report. Unfortunately I can't reproduce it on 262766@main (macOS). Could someone with a trunk gtk build check it out, please?
Michael Catanzaro
Comment 2 2023-04-10 08:08:41 PDT
Broken here with 262767@main. I'm surprised this one is platform-specific, but OK.
zalan
Comment 3 2023-04-10 08:22:31 PDT
Created attachment 465829 [details] screenshot on macOS Yeah, it is odd.
Abrar Ahmed
Comment 4 2023-04-11 06:38:50 PDT
Created attachment 465844 [details] Text is rendered when zoomed in I've found something odd. Text gets rendered properly when I zoom in using the trackpad gesture.
Abrar Ahmed
Comment 5 2023-04-16 06:07:07 PDT
The YouTube notifications popover also seems to display this same behaviour
Abrar Ahmed
Comment 6 2023-08-11 09:59:02 PDT
The bug seems to have been fixed. The text in the gtk-rs book is now being rendered properly. I tried the site with both the stable and tech preview of epiphany. I'll close this ticket.
Note You need to log in before you can comment on or make changes to this bug.