W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2017

Re: [csswg-drafts] [css-fonts] Consider specifying UA should not perform system fallback for Unicode PUA

From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
Date: Mon, 18 Dec 2017 14:04:32 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-352434171-1513605871-sysbot+gh@w3.org>
> How would the (U+F8FF Apple Logo) character work? I don’t think anyone explicitly lists the specific font it’s in.

I guess if we standardize the recommendation as "should", you could make an exception for U+F8FF? Or use 🍏 + VS15? Or propose to standardize something in Unicode, e.g. GENERIC CORP LOGO + TAG SEQUENCE...TAG TERM for corporate logos? 

On a more serious note: The background for this proposal is that the PUA semantics are defined to be custom to the font - using system wide fallback for them is highly unlikely to return meaningful results to avoid .notdef's.

> Does any browser currently have this proposed behavior?

[We're implementing it in Blink](https://bugs.chromium.org/p/chromium/issues/detail?id=795225) after we discovered that we occasionally receive unsuitable fallback results from the system when querying for PUA codepoints while for example a web icon font has not loaded yet.

GitHub Notification of comment by drott
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2110#issuecomment-352434171 using your GitHub account
Received on Monday, 18 December 2017 14:04:34 UTC

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