• unknowing8343
    link
    fedilink
    arrow-up
    2
    ·
    3 days ago

    In which situation does it make sense for Firefox to call for it instead of you yourself? This seems like bloatware to me.

    • Vincent@feddit.nlOP
      link
      fedilink
      arrow-up
      1
      ·
      2 days ago

      What would it mean for you to call it yourself? This change is just so that if you press Ctrl+. in Firefox, the native emoji picker shows up, so at least in that sense you’re invoking it yourself? (Before this change, Ctrl+. would do nothing in Firefox, even though it would show the emoji picker in normal GTK applications.)

      • unknowing8343
        link
        fedilink
        arrow-up
        1
        ·
        1 day ago

        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.

          • unknowing8343
            link
            fedilink
            arrow-up
            1
            ·
            17 hours ago

            Not even that, because Gnome probably already has a shortcut for the emoji picker.

            • Vincent@feddit.nlOP
              link
              fedilink
              arrow-up
              1
              ·
              15 hours ago

              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.)

                • Vincent@feddit.nlOP
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  1 hour ago

                  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.