Bug 112520

Summary: css text-rendring property breaking utf-8 special chars and switching font-face
Product: WebKit Reporter: Simon Boudrias <admin>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Minor CC: ahmad.saleem792, bfulgham, rniwa, simon.fraser, zalan
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows 7   
URL: http://jsbin.com/uqisib/8/edit
Attachments:
Description Flags
Reduced test case rendering screenshot none

Simon Boudrias
Reported 2013-03-17 13:51:03 PDT
`text-rendering` css property is causing some pretty bad issue on Windows Chrome (tested under v25). Some special UTF-8 characters won't render correctly (using the unknown char square) and some text section can change font-face (even from sans-serif to serif). I created a reduced test case here: http://jsbin.com/uqisib/8/edit + First title is the default _Twitter Boostrap_ theme breaking an UTF-8 char + Second use _impact_ font-face to clearly visualize the bug (utf-8 special char not showing and font-face switching) + Third title just remove the text-rendering property to show the visual bug is resolved and is not related directly to the font-face
Attachments
Reduced test case rendering screenshot (9.11 KB, image/png)
2013-03-17 13:51 PDT, Simon Boudrias
no flags
Simon Boudrias
Comment 1 2013-03-17 13:51:48 PDT
Created attachment 193472 [details] Reduced test case rendering screenshot
Ahmad Saleem
Comment 2 2022-08-06 19:58:13 PDT
I am unable to reproduce this bug in Safari 15.6 on macOS 12.5 and from attached test case, I can see that it is rendering 'flower' correctly rather than "block" of unknown character from the reference screenshot. I am going to mark this as "RESOLVED CONFIGURATION CHANGED". NOTE - All other browsers (Firefox Nightly 105 and Chrome Canary 106) also render "flower" character rather than "unknown" character block. Further, I also updated HTTP to HTTPS to ensure that I don't get any console warning about not able to load resources etc.
Note You need to log in before you can comment on or make changes to this bug.