3 ms·

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

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.

embedding-shape 6mo ago
> 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.
Wowfunhappy 6mo ago
Okay, in that case, I completely misunderstood the issue. If the change is that Firefox now allows the system-level picker to get through instead of blocking the keyboard shortcut, that’s a win. I thought Firefox was adding its own Emoji-picker UI.
- embedding-shape 6mo ago
  > If the change is that Firefox now allows the system-level picker to get through instead of blocking the keyboard shortcut, that’s a win. You're almost there :) Firefox now opens the system-level picker for that shortcut, regardless of what global keyboard shortcut you might have configured system-level. So system-level, I have nothing done on "CTRL + .", in Firefox, I have 1Password browser extension triggered by "CTRL + ." so when Firefox version 150 was launched, instead of seeing 1Password when I did the shortcut, it instead showed my system-level emoji picker (which I have no shortcut for), triggered by Firefox.
  - Wowfunhappy 6mo ago
    Okay, now I’m back to being annoyed. :) Why can’t Firefox respect system-level custom keyboard shortcuts? This has been a bug on Mac for like 15 years and they don’t seem to care about it at all, which IMO is ridiculous, it’s core system functionality.
    - deleted 6mo ago
      [deleted]

embedding-shape 6mo ago

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

Wowfunhappy 6mo ago

Okay, in that case, I completely misunderstood the issue. If the change is that Firefox now allows the system-level picker to get through instead of blocking the keyboard shortcut, that’s a win. I thought Firefox was adding its own Emoji-picker UI.

embedding-shape 6mo ago
> If the change is that Firefox now allows the system-level picker to get through instead of blocking the keyboard shortcut, that’s a win. You're almost there :) Firefox now opens the system-level picker for that shortcut, regardless of what global keyboard shortcut you might have configured system-level. So system-level, I have nothing done on "CTRL + .", in Firefox, I have 1Password browser extension triggered by "CTRL + ." so when Firefox version 150 was launched, instead of seeing 1Password when I did the shortcut, it instead showed my system-level emoji picker (which I have no shortcut for), triggered by Firefox.
- Wowfunhappy 6mo ago
  Okay, now I’m back to being annoyed. :) Why can’t Firefox respect system-level custom keyboard shortcuts? This has been a bug on Mac for like 15 years and they don’t seem to care about it at all, which IMO is ridiculous, it’s core system functionality.
  - deleted 6mo ago
    [deleted]