Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

typography field doesn't list standard font-families (Arial, Verdana ... #1252

Closed
kmob2 opened this issue Jan 16, 2017 · 1 comment
Closed
Milestone

Comments

@kmob2
Copy link

kmob2 commented Jan 16, 2017

This is a follow up to issue #1189 - It's closed but I can't seem to open it again.


Hello aristath,

Sorry for opening this up again. I'm only just now continuing the typography on my theme.

I am very confused on why you would group the standard fonts together by "style".
Serif is not a font (typeface) by itself. Serif refers to if a font has a stroke a in their symbols or not. https://en.wikipedia.org/wiki/Serif - Respectively sans serif is without the stroke.

Grouping them all together doesn't really make sense to me, since they are all completely different looking fonts.
In css using font-family, if you have multiple fonts listed, they work as backups.

Example: font-family: "Times New Roman", Times, serif;
The browser first looks if the font Times New Romand is available, if nothing is found, then it looks for Times (which is similar), if again nothing is found, then it looks for all fonts styles that use serif.

The way the typography field currently is in kirki, is that if I select sans serif it outputs 'Monaco,"Lucida Sans Typewriter","Lucida Typewriter","Courier New",Courier,monospace', which are a group of completely different looking fonts, and since only the first one is being used by the browser, because they rest acts as backups, I have no way of selecting for example Courier New.

I really think all the standard web fonts as listed here: http://www.w3schools.com/cssref/css_websafe_fonts.asp should have their own selection field in the drop down. This current way of grouping them together is not really the way the fonts should be used.

@aristath
Copy link
Contributor

aristath commented Feb 4, 2017

Replied on #1189 (comment)

@aristath aristath closed this as completed Feb 4, 2017
@aristath aristath modified the milestone: 3.0 Apr 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants