New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 768245 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 3
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Font names with blanks followed by a nurmerical digit can't be used like other fontnames with a blank

Reported by 1der1...@gmail.com, Sep 24 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Steps to reproduce the problem:
1. Load the font "Exo 2" for example
2. Try to use it with Chrome
3. 

What is the expected behavior?
<font face="Times New Roman">Hello World</font> works
<font face="Exo 2">Hello World</font> should work as well

What went wrong?
If a font name contains a blank followed by a numerical digit, it requires an extra quoting.

<font face="Exo 2">Hello World</font>
does not work, but

<font face="'Exo 2'">Hello World</font>
works.

The problem is not only related to the font tag but shows up in all cases where you provide a font family to Chrome.

Sometimes it is difficult to provide the extra quoting. The following piece of code fails with fonts like "Exo 2":

var li = $( "<li>" ), wrapper = $( "<div>",
{ text: item.label,
  "style" : "font-family:'"+ (item.value || Roboto')+"'"} );

Did this work before? No 

Chrome version: 60.0.3112.113  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

Firefox does not have this issue.

"Exo 2", "Goudy Bookletter 1911" and all the Slabo fonts "Slabo 13px", etc. are on the Google font page:
https://fonts.google.com/?query=exo&selection.family=Exo+2

Of course, 
<font face="Exo+2">Hello World</font>
does not work either
 

Comment 1 by 1der1...@gmail.com, Sep 25 2017

I made a 20 seconds video about testing the fonts in our web page builder:
https://www.youtube.com/watch?v=rfC1PlK87jU
Labels: Needs-Milestone
Cc: sc00335...@techmahindra.com
Components: Blink>Fonts
Labels: Triaged-ET Needs-Feedback
Unable to reproduce this issue on reported version 60.0.3112.113 , on latest canary 63.0.3223.8 using windows 10,Ubuntu 14.04 with steps mentioned below.

1.Opened attached html file which has <font face="Exo 2">Hello World</font> , <font face="'Exo 2'">Hello World</font> and <font face="Exo+2">Hello World</font>.
2.All 3 returned same result. Attaching screenshot of result and .html file used to check.

@Reporter: Could you please let us know whether we missed anything ? Or Could you please attach sample file to check further from chrome TE end.

Thanks.
768245.png
6.0 KB View Download
Issue 768245
381 bytes View Download

Comment 4 by woxxom@gmail.com, Sep 26 2017

#3, your test html sets a default font on BODY via CSS, which is used for the 2nd <font face="Exo 2">
Use the fixed html attached here.
test.html
413 bytes View Download

Comment 5 by e...@chromium.org, Sep 30 2017

Cc: drott@chromium.org
Labels: -Pri-2 Pri-3
Status: Available (was: Unconfirmed)
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 1

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: futhark@chromium.org
Components: Blink>CSS
Status: Available (was: Untriaged)
Status: WontFix (was: Available)
This is per spec for the <family-name> syntax. Same result in Gecko.

Sign in to add a comment