Control + f ends up going to Discourse search when the expectation is browser search. I know the development team has their reasons but sometimes it’s more useful to search for keywords within a post. How can I disable it so that control + f is disabled? I know the dev team will defend their reas…

Thank you for the tip. It is unusual that Control+F works as expected for topics or posts with few replies but switches to Discourse search when there are multiple replies. This is not obvious and can cause confusion. Users who need to search within Discourse can press the magnifying glass icon, sim…

I see it as more of an extension than overriding the function. Ctrl+F means “I am looking for a specific string on this page”. But if the text is in the topic but hasn’t been loaded in, you won’t find it, but the search will. I think it’s unreasonable to expect the user to understand the pagination…

See post attached for more thorough discussion. [image] Remove overriding of cmd/ctrl-f UX How to recreate: Use major browsers (chromium derivatives / ffx / ie) browse the internet become accustomed to using standard keyboard commands like cmd-q, cmd-1/2/3, …

Disabling Ctrl-F

Support

piffy May 17, 2024, 11:00pm 2

You can press ctrl+f twice to use the native browser search

Topic		Replies	Views
Discourse taking over Ctrl-F Feature	21	14257	October 5, 2014
Discourse no longer hijacks ctrl+f? Support search , keyboard-shortcuts	5	254	February 12, 2026
Remove overriding of cmd/ctrl-f UX keyboard-shortcuts	34	1548	June 20, 2024
Pressing Ctrl+F twice on topic search should close the Discourse search window Feature	19	6181	February 18, 2016
Ctrl-f gave me a spinning wheel Feature	6	1483	May 9, 2016

Disabling Ctrl-F

Related topics