I've assigned "Find..." and "Find" titles to Ctrl+F in Chrome and also under All Applications, in Keyboard settings.

However, it doesn't work inside text boxes in Chrome, and I have to use Cmd+F instead.

The same happens with Ctrl+A for example.

It works elsewhere.

  • Welcome to Ask Different. If an app like chrome or Firefox implements custom key handling and doesn’t pass them to the system that is a design decision the app maker made. What specifically is your question?
    – bmike
    Apr 27, 2022 at 12:00
  • It works in Chrome, but doesn't work inside textboxes in Chrome. Even the textbox here where I'm typing to you. But when I'm using Ctrl+F somewhere outside the textbox, it does work.
    – Tom S
    Apr 27, 2022 at 12:34
  • Chrome would need to enable standard text control within those text boxes for the shortcuts to get processed.
    – bmike
    Apr 27, 2022 at 16:12
  • I think this may be related to the Responder Chain. Ctrl+X are mostly used for text editing in textviews.
    – hym3242
    May 17 at 12:27

1 Answer 1


Choosing where to allow copy, paste and undo is the first thing a developer needs to decide. Next is how many undo and if state is saved. Lastly, they have to decide where shortcuts get processed within the app.

  • Do they choose to allow undo when you press space to page down and scroll web page content?
  • Do they allow search (and/or) replace within a text input field?

These are decisions chrome made on how to handle keyboard input. You might have to open a bug with them if you don’t like or understand how they implemented it. I see this as works as designed even though I (think I) understand your statement here.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .