NEW 258050
synthetic bold applied on top of bold font variant?
https://bugs.webkit.org/show_bug.cgi?id=258050
Summary synthetic bold applied on top of bold font variant?
Karl Dubost
Reported 2023-06-13 15:57:01 PDT
Created attachment 466683 [details] webarchive of the page with the issue. Steps to reproduce: 1. With Safari Tech Preview 172 2. Go to https://css-irl.info/thoughts-from-css-day-2023/ Expected: Elegant bold fonts on titles and strong elements. Actual: Notice how the font becomes very bold and less readable.
Attachments
webarchive of the page with the issue. (301.93 KB, application/x-webarchive)
2023-06-13 15:57 PDT, Karl Dubost
no flags
rendering in safari, firefox, edge (249.94 KB, image/png)
2023-06-13 15:58 PDT, Karl Dubost
no flags
rendering in safari, firefox, edge (493.43 KB, image/png)
2023-06-13 16:00 PDT, Karl Dubost
no flags
rendering in safari, firefox, chrome (90.25 KB, image/png)
2024-07-28 21:02 PDT, Karl Dubost
no flags
rendering in safari, firefox, chrome (retina) (276.59 KB, image/png)
2024-07-28 21:03 PDT, Karl Dubost
no flags
testcase (565 bytes, text/html)
2024-07-28 21:04 PDT, Karl Dubost
no flags
Radar WebKit Bug Importer
Comment 1 2023-06-13 15:57:14 PDT
Karl Dubost
Comment 2 2023-06-13 15:58:58 PDT
Created attachment 466684 [details] rendering in safari, firefox, edge From left to right: WebKit, Gecko and Blink
Karl Dubost
Comment 3 2023-06-13 16:00:42 PDT
Created attachment 466685 [details] rendering in safari, firefox, edge
Karl Dubost
Comment 4 2024-07-28 21:02:26 PDT
Created attachment 471997 [details] rendering in safari, firefox, chrome on a 1x screen.
Karl Dubost
Comment 5 2024-07-28 21:03:15 PDT
Created attachment 471998 [details] rendering in safari, firefox, chrome (retina) Rendering on a retina screen.
Karl Dubost
Comment 6 2024-07-28 21:04:00 PDT
Created attachment 471999 [details] testcase This is what I have used.
Karl Dubost
Comment 7 2024-07-28 21:04:42 PDT
@Elika, this seems related to the differences of font-weight:800 on a 1x screen vs a retina screen.
Note You need to log in before you can comment on or make changes to this bug.