W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2019

Re: [csswg-drafts] [css-fonts] Don't require browsers to always match every generic font family to a concrete font family (#4442)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Tue, 29 Oct 2019 18:45:51 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-547573608-1572374750-sysbot+gh@w3.org>
Agree, option 1 seems best all around.

Looping back to @frivoal's earlier question:

>  If we do go with behavior 1, in order to set author's expectations it would be useful to specify whether:
> 
> * the fallback must be independent of the specified font stack
> * the fallback may be influenced by the last font in the specified font stack if it is generic
> * the fallback may be influenced by the last generic font in the specified font stack, even if it is followed by non generics
> * the fallback may be influenced by [... some other specific thing ...]
> * the fallback may be influenced by the specified font stack in arbitrary ways up to the UA

Any opinions? @koji seems to be suggesting it's the last one (influenced in arbitrary UA-specific ways) in Chrome.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4442#issuecomment-547573608 using your GitHub account
Received on Tuesday, 29 October 2019 18:45:52 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:55 UTC