- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Sat, 02 Jul 2022 01:39:04 +0000
- To: public-css-archive@w3.org
My intuition for what `unicode-range` is supposed to do matches what you describe in option 1 (which may be equivalent to option 2). I don't think that counts for much, though. On the other hand, one real compatibility concern might be that if some implementations do (3), developers might observe an implementation doing (3) and start depending on it, i.e., start expecting browsers to use the font for characters outside of its declared `unicode-range`. So it's possible that option (3) might be problematic if it were allowed but not required. I think this is particularly an issue when the fonts involved have glyphs that don't, um, correspond to what Unicode says should be shown for the codepoints in question. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7449#issuecomment-1172809704 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 2 July 2022 01:39:06 UTC