Re: [css-fonts] Proposal for standardizing font timeout behavior

> On Oct 30, 2014, at 7:09 AM, Jonathan Kew <jfkthame@gmail.com> wrote:
> 
> On 30/10/14 13:36, Brad Kemper wrote:
> 
> >> I'm guessing the 'mandatory <infinite>' for
>>> Safari is just a bug not really a feature.
>> 
>> It is kind of crazy to have that for everything, but I think
>> 'mandatory infinite' would be useful for icon/picture fonts. Or, if
>> not 'infinite', then some sort of keyword to make it fall back to a
>> generic glyph (such as a square), instead of whatever letter the icon
>> is mapped to. .
>> 
> 
> What's this about "whatever letter the icon is mapped to"?!
> 
> Icon glyphs should not be mapped to letters. They should be mapped to the appropriate Unicode symbols/dingbats/emoji/whatever (which means applying browser font fallback is perfectly reasonable); or if the icon concerned is not encoded in Unicode, then to Private Use Area codepoints (for which browsers shouldn't be attempting font fallback at all; see CSS3-Fonts[1]).

That sounds like a fine idea. Do most dingbat fonts do that these days?