Heh fair :) For the lack of a better icon to use, I did copy paste a emoji to be used as the favicon, I hope my readers can eventually forgive me for this transgression.
> On GNOME we already have a global shortcut for some emoji picker, I think it's Super + , or something
Actually, on most distros, the default keyboard shortcut for the emoji picker on GNOME/GTK is ctrl-. (same as the Firefox shortcut). This only works on apps that support it. Older Firefox versions did not support GNOME's emoji picker at all, but Firefox 150 supports GNOME's emoji picker using the expected keyboard shortcut.
To me this is more or less why Firefox is as dead as it is. They can't even fix what is a legitimate system level incompatibility without people loudly getting upset. They basically have no path forward.
> the default keyboard shortcut for the emoji picker on GNOME/GTK is ctrl-. (same as the Firefox shortcut).
Hmm, I wonder how new that is? Could be possible that my GNOME installation is old enough to predate that, and they didn't overwrite the config like Firefox did? Because I've been using Firefox + 1Password + GNOME for years, and for as long as I can remember, `ctrl + .` has opened 1Password dialogue in Firefox, and I'm not sure I've ever seen an Emoji picker in GNOME, although I know it exists somewhere.
An Emoji picker should be an OS-level feature. If the OS doesn’t provide the feature, then that is the OS’s decision to make, and the browser should respect it.
Why would I want text input in one app to have a feature that text input in other apps lacks?
It is an OS-level feature, or at least desktop environment level. Far as I know, it's always been Ctrl-. or Ctrl-; for any GTK app, but Firefox had apparently bound Ctrl-. to something else. So basically, this "added" feature is Firefox getting out of the way of the built-in picker that was already there.
On macOS, it still opens the multi-account container panel, and the emoji picker is still brought up by tapping Fn.
> but Firefox had apparently bound Ctrl-. to something else.
I think up until version 150 it was nothing, as 1Password had `ctrl + .` as the default shortcut for opening up their autocomplete thing, and feels like they wouldn't have chosen that shortcut years ago if Firefox was already using it for something, but maybe I misremember.
This is an "OS"-feature, where OS means the GUI-Framework that Firefox is using to integrate with the DE.
> If the OS doesn’t provide the feature, then that is the OS’s decision to make, and the browser should respect it.
That's a very strange claim. Nearly everything in any app is something the OS is not providing; that's why apps exist in the first place, to enhance the environment.
> Why would I want text input in one app to have a feature that text input in other apps lacks?
Why should they cripple themselves willingly; just to align with others? Especially as this is a web browser, which has become the main way of interaction with a big part of the world.
> then you end up with a different interface everywhere.
This whole post is about someone being upset that Firefox finally did support the system level interface and shortcut. And you're upset about that while asking for consistent interfaces. Some people can just never be happy I guess.
I understand that, but as someone who was an engineer at both Microsoft and Apple, I see absolutely no problem with 3rd-parties adding useful features.
As I said, as long as 3rd parties aren't overriding the built-in functionality by default (e.g., using the same keyboard shortcuts), there's no problem. 99% of FF users will probably never even know it has its own picker.
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.
I'm on Firefox 150.0.1 on Windows, and Ctrl+. consistently opens up the Firefox Multi-Account Containers panel, regardless of hitting that shortcut while focusing this same text box I'm writing on right now, or not.
So this sounds like not working as expected I guess.
So it makes sense that they do not get the emoji picker, as they are in windows. I use macos and I also get the multiacccount container. On macos the emoji system-wide shortcut is ctrl+cmd+space.
Oh, totally yes, missed that they wrote that, thanks! This change from Firefox only applies to Linux, so Windows and macOS users shouldn't notice any difference compared to before in regards to `ctrl + .` as far as I understand.
On my case, It opnes the KDE emoji picker ... But this emoji picker walys show with that key combination in any program. I think that Firefoxs nevers gets the Ctrl+. key shortcut
The Firefox UI is getting worse and worse with every version, because they are constantly adding more useless features. Any time you accidentally hit the wrong button, it launches something, because everything is a shortcut now. The latest being their split tabs, which I also had to disable. Maybe they should stop trying to turn their browser into an OS.
> I don't really write any emojis in anything I use a browser for anyways
Proceeds to use an emoji as favicon :D
Heh fair :) For the lack of a better icon to use, I did copy paste a emoji to be used as the favicon, I hope my readers can eventually forgive me for this transgression.
> On GNOME we already have a global shortcut for some emoji picker, I think it's Super + , or something
Actually, on most distros, the default keyboard shortcut for the emoji picker on GNOME/GTK is ctrl-. (same as the Firefox shortcut). This only works on apps that support it. Older Firefox versions did not support GNOME's emoji picker at all, but Firefox 150 supports GNOME's emoji picker using the expected keyboard shortcut.
To me this is more or less why Firefox is as dead as it is. They can't even fix what is a legitimate system level incompatibility without people loudly getting upset. They basically have no path forward.
> the default keyboard shortcut for the emoji picker on GNOME/GTK is ctrl-. (same as the Firefox shortcut).
Hmm, I wonder how new that is? Could be possible that my GNOME installation is old enough to predate that, and they didn't overwrite the config like Firefox did? Because I've been using Firefox + 1Password + GNOME for years, and for as long as I can remember, `ctrl + .` has opened 1Password dialogue in Firefox, and I'm not sure I've ever seen an Emoji picker in GNOME, although I know it exists somewhere.
An Emoji picker should be an OS-level feature. If the OS doesn’t provide the feature, then that is the OS’s decision to make, and the browser should respect it.
Why would I want text input in one app to have a feature that text input in other apps lacks?
It is an OS-level feature, or at least desktop environment level. Far as I know, it's always been Ctrl-. or Ctrl-; for any GTK app, but Firefox had apparently bound Ctrl-. to something else. So basically, this "added" feature is Firefox getting out of the way of the built-in picker that was already there.
On macOS, it still opens the multi-account container panel, and the emoji picker is still brought up by tapping Fn.
> but Firefox had apparently bound Ctrl-. to something else.
I think up until version 150 it was nothing, as 1Password had `ctrl + .` as the default shortcut for opening up their autocomplete thing, and feels like they wouldn't have chosen that shortcut years ago if Firefox was already using it for something, but maybe I misremember.
> An Emoji picker should be an OS-level feature.
This is an "OS"-feature, where OS means the GUI-Framework that Firefox is using to integrate with the DE.
> If the OS doesn’t provide the feature, then that is the OS’s decision to make, and the browser should respect it.
That's a very strange claim. Nearly everything in any app is something the OS is not providing; that's why apps exist in the first place, to enhance the environment.
> Why would I want text input in one app to have a feature that text input in other apps lacks?
Why should they cripple themselves willingly; just to align with others? Especially as this is a web browser, which has become the main way of interaction with a big part of the world.
Allow me to rephrase: If the OS doesn’t provide X, the end user should have no alternative for X.
I use both macOS and Pop!OS. The latter doesn't include an emoji picker by default, so I'm precluded from using a 3rd-party picker?
There is no issue as long as a 3rd-party app doesn't override built-in functionality. If you don't want it, it is easy to disable.
Especially on a Linux distro, you could install a 3rd-party package that adds an emoji picker system-wide, as opposed to in one app.
If every app brings its own emoji picker, then you end up with a different interface everywhere.
> then you end up with a different interface everywhere.
This whole post is about someone being upset that Firefox finally did support the system level interface and shortcut. And you're upset about that while asking for consistent interfaces. Some people can just never be happy I guess.
I understand that, but as someone who was an engineer at both Microsoft and Apple, I see absolutely no problem with 3rd-parties adding useful features.
As I said, as long as 3rd parties aren't overriding the built-in functionality by default (e.g., using the same keyboard shortcuts), there's no problem. 99% of FF users will probably never even know it has its own picker.
I mean, Firefox is 3rd party, so.
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.
I'm on Firefox 150.0.1 on Windows, and Ctrl+. consistently opens up the Firefox Multi-Account Containers panel, regardless of hitting that shortcut while focusing this same text box I'm writing on right now, or not.
So this sounds like not working as expected I guess.
Might depend on when you first launched Firefox, so it tries to "grandfather" some settings across the versions?
That `ctrl + .` now opens the emoji picker on Linux seems to very much be intended, judging by this release post: https://www.firefox.com/en-US/firefox/150.0/releasenotes/
> Added support for the GTK emoji picker on Linux, allowing users to insert emoji using the system shortcut (typically Ctrl+.).
>> Windows
> Linux [...] system shortcut
So it makes sense that they do not get the emoji picker, as they are in windows. I use macos and I also get the multiacccount container. On macos the emoji system-wide shortcut is ctrl+cmd+space.
Oh, totally yes, missed that they wrote that, thanks! This change from Firefox only applies to Linux, so Windows and macOS users shouldn't notice any difference compared to before in regards to `ctrl + .` as far as I understand.
Odd, I am on firefox 150, and Ctrl + . doesn't seem to do anything.
What OS? Might just be while focused in text inputs as well, in case you've been trying it without an input.
On my case, It opnes the KDE emoji picker ... But this emoji picker walys show with that key combination in any program. I think that Firefoxs nevers gets the Ctrl+. key shortcut
Is Firefox turning into Edge?
The list of things I don't want in a browser is growing.
Perhaps they need to consider a "basic" version
> Annoyingly enough, Mozilla decided to add a emoji picker to Firefox 150, which fair enough, probably some people like
Mozilla is really focusing on how to break the Google monopoly.
With the POWER of the Emoji, Mozilla will succeed here. I ... suppose?
They break the Google monopoly by being funded by Google so that Google can say there is an alternative
Yep. Blatant controlled opposition.
Ladybird browser can't come soon enough.
The Firefox UI is getting worse and worse with every version, because they are constantly adding more useless features. Any time you accidentally hit the wrong button, it launches something, because everything is a shortcut now. The latest being their split tabs, which I also had to disable. Maybe they should stop trying to turn their browser into an OS.