After nearly three years of development (it takes time to make up one’s mind) Firefox for Linux users can now enjoy seamless emoji insertion using the native GTK emoji chooser. This long-requ…
The thing is that I can already do Super+. (or was it ,, can’t remember now) and I get shown my emoji picker (which is not the GTK one, but the KDE one) for ANY app that I am using. No need for Firefox to help me on that.
Yes, but that didn’t work in Firefox before this change. The whole point of this change is to make that work in Firefox as well. (Likewise, it still doesn’t work in Chrome, Chrome-based browsers, and Electron apps.)
It’s not so much that they’re blocking it, as it is that they’re not implementing it. In GNOME, as I understand it, the Emoji picker is implemented by the toolkit (GTK). That means that apps that don’t (fully) use that toolkit, such as Chrome and Firefox, will need to add the implementation themselves. That is now done for Firefox.
The thing is that I can already do
Super+.(or was it,, can’t remember now) and I get shown my emoji picker (which is not the GTK one, but the KDE one) for ANY app that I am using. No need for Firefox to help me on that.So the situation in which this makes sense is when you’re using Gnome.
Not even that, because Gnome probably already has a shortcut for the emoji picker.
Yes, but that didn’t work in Firefox before this change. The whole point of this change is to make that work in Firefox as well. (Likewise, it still doesn’t work in Chrome, Chrome-based browsers, and Electron apps.)
How could Firefox or Chrome block a system shortcut??
It’s not so much that they’re blocking it, as it is that they’re not implementing it. In GNOME, as I understand it, the Emoji picker is implemented by the toolkit (GTK). That means that apps that don’t (fully) use that toolkit, such as Chrome and Firefox, will need to add the implementation themselves. That is now done for Firefox.