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…

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

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. [이미지] 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, cm…

Ctrl-F 비활성화

지원

piffy 5월 17, 2024, 11:00오후 2

Ctrl+F를 두 번 누르면 브라우저의 기본 검색 기능을 사용할 수 있습니다.

글		댓글	조회수
Discourse taking over Ctrl-F Feature	21	14257	10월 5, 2014
Discourse no longer hijacks ctrl+f? Support search , keyboard-shortcuts	5	254	2월 12, 2026
Remove overriding of cmd/ctrl-f UX keyboard-shortcuts	34	1548	6월 20, 2024
Pressing Ctrl+F twice on topic search should close the Discourse search window Feature	19	6181	2월 18, 2016
Ctrl-f gave me a spinning wheel Feature	6	1483	5월 9, 2016

Ctrl-F 비활성화

Related topics