- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Mar 2018 10:18:50 +0000
- To: public-css-archive@w3.org
> I've tested Chrome and Firefox, and both don't do any system font fallback when the given font contains a glyph for the `b` but don't for `b + c1`. Yep, browser support for variation selectors is quite lacking right now. I don't know of any browser which handles them correctly. > The spec should either be amended to reflect the behavior implemented by browsers, or the browser's behavior should be changed. Yep, the browser's behavior should be changed. > The fallback to `b` behavior is problematic because it may not be what the author intended and the user has completely no idea. More often, the preferred behavior is that a "tofu" (.nodef) is displayed instead. Yep, this is why I wrote the spec to describe this behavior as required. > In these cases, getting .nodef is usually preferred over getting the base character's glyph if a given font doesn't have that specific glyph variant. Yep. > These behaviors could be implemented via a new CSS property such as `font-variation-sequences` I don't think this is worth a whole new property. Control over these facilities already exists in the form of variation selectors. The niche applications which need to perform their own handling of these characters can use Javascript to implement their desired behavior. -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1710#issuecomment-370733495 using your GitHub account
Received on Tuesday, 6 March 2018 10:18:52 UTC