> Am 31.05.2024 um 13:05 schrieb Paul W. Rankin <hello@paulwrankin.com>:
> 
> 
>> On 31 May 2024, at 19:53, Omar Polo <op@omarpolo.com> wrote:
>> 
>> On 2024/05/31 15:23:25 +1000, "Paul W. Rankin" <hello@paulwrankin.com> wrote:
>>> It looks like the original email was blackholed. Here it is again...
>>> 
>>> This patch adds the CSS property font-variant-emoji: text to the 
>>> directory index. When supported this property prevents the unicode "up 
>>> and down" arrow being displayed as an emoji. Currently this property 
>>> needs to be explicitly enabled by users in Firefox and Safari, but will 
>>> hopefully be default soon.
>>> 
>>> More info:
>>> https://developer.mozilla.org/en-US/docs/Web/CSS/font-variant-emoji
>> 
>> so this should prevent future browsers from rendering the "up and down"
>> character in colours.  the mdn page is a bit vague in terms of what will
>> be the default value, saying that it's os-dependant.
>> 
>> however, i'm for a more sober design, and the cost of keeping one css
>> property is negligible.
> 
> 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


Mike