On 2024/05/31 23:20:59 +1000, "Paul W. Rankin" <hello@paulwrankin.com> wrote:
> 
> > On 31 May 2024, at 22:46, Mike Fischer <fischer+obsd@lavielle.com> wrote:
> > 
> >> Kind of. Currently browsers can choose to render some unicode 
> >> characters as emojis instead of text. For reference, this is what the 
> >> auto index page looks like in iOS Safari: https://0x0.st/XN6y.png
> >> 
> >> This CSS property will, at a point in the future, ensure the unicode 
> >> text is displayed as the original text instead of replaced with emojis. 
> >> Browser support for this property currently requires the user 
> >> explicitly enable it in Firefox and Safari.
> > 
> > That is fine. In the mean time you could just use this to avoid the emoji substitution:
> > content: "\a0\2195\fe0e";
> > 
> > See: https://developer.mozilla.org/en-US/docs/Web/CSS/font-variant-emoji
> 
> I think this is the preferable solution. It works now without users 
> explicitly enabling aa CSS property. New patch attached.

mmhhh, not sure.  I've just committed the previous diff (was worth it at
least for the removal of the italic! :P).  I can see how this can work
as well, but it I personally find a bit ugly to just throw a few hex
like that (and also find ugly this idea of using these variants to
change the presentation of the text).

but fwiw i wont oppose if it's preferred.


Thanks!