Hmmm. Let me preface here that I think Mozilla invests its energy in a strange way.

On the other hand, I am not sure I can agree with "OS-level feature".

An emoji is essentially something simple, right? I am thinking of an "Unicode symbol" here. So to me, I would like to use any emoji or unicode as-is, anywhere, when it comes to user input - copy/paste, perhaps even converting it to a real image. You mentioned that "browsers should respect if emojis are forbidden by the OS", in essence, and I am not sure I agree with that. If an OS does not allow me to use an emoji, then I would not want to use that OS (well, I use Linux, so that does not matter anyway; and I avoid GNOME since it is too opinionated - I want to decide what I can do, I don't want remote developers decide what to do; this is also why I stopped using KDE, after the donation-daemon was added by Nate not so long ago).

> Why would I want text input in one app to have a feature that text input in other apps lacks?

That is a valid question but would I want to give up on emojis because "the OS does not support it"? I'd much rather use emojis, even IF an OS does not support it. I really don't want to be limited like that by an OS.

Perhaps this simply refers to different assumptions. I think we can agree that Mozilla invests their resources in a strange way though.