New issue
Advanced search Search tips

Issue 867387 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jul 27
Cc:
susan.boorgula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome's default fonts missing latin-ext characters (at the very least háček(caron)-accented letters ěščřž), those fall back to monospace font

Reported by ond...@gmail.com, Jul 25 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36

Steps to reproduce the problem:
1. Install google-chrome-unstable from PPA
2. type in ěščřžýá characters (presumably others as well) anywhere or view a webpage with any such characters in it. (www.seznam.cz comes to mind)
3. See those render in a monospace font (Courier New presumably)

What is the expected behavior?
The browser's default sans-serif font should cover most conceivable subsets of UTF8.

What went wrong?
The browser's (unstable dev versiono) default sans-serif font is missing these characters and they get rendered differently

Did this work before? N/A 

Chrome version: 69.0.3493.3 (Official Build) dev (64-bit)  Channel: stable
OS Version: Ubuntu 18.04 LTS
Flash Version: 30.0.0.142 /home/ondra/.config/google-chrome-unstable/PepperFlash/30.0.0.142/libpepflashplayer.so

Upon re-installing Chrome 68 stable, unstable switched from the new light and rounded UI skin back to dark which uses a different font, this one supports the given characters well (the viewport still suffers though)
Screenshot from 2018-07-25 13-00-25.png
47.3 KB View Download

Comment 1 by ond...@gmail.com, Jul 25 

Edit: Browser chrome seems to be using a compatible font even in light UI mode now, so false alarm.
Also, the user agent info at the top is wrong as I wrote this from the Stable release. Please respect the post contents.
(Wish I could edit the original post so as to avoid confusion.)
Screenshot from 2018-07-25 13-35-12.png
17.5 KB View Download

Comment 2 by susan.boorgula@chromium.org, Jul 25

Labels: Needs-Triage-M69

Comment 3 by susan.boorgula@chromium.org, Jul 26

Cc: susan.boorgula@chromium.org
Labels: Needs-Feedback Triaged-ET
ondtka@ Thanks for the issue.

This issue looks to be similar to  issue 857511  which was fixed on chrome version 69.0.3494.0.
Request you to retry the issue on the latest Dev 69.0.3497.12 and confirm if the issue is resolved or not.

Thanks..

Comment 4 by ond...@gmail.com, Jul 26 

 susan.boorgula@ 
This has indeed been resolved by the update and no longer happens for me on 69.0.3497.12
Thank you very much. You can probably close this issue.
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 26

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by ajha@chromium.org, Jul 27

Status: WontFix (was: Unconfirmed)
Closing as per C#3.
►

Sign in to add a comment