Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Mozilla サポートの検索

サポート詐欺に注意してください。 私たちはあなたに通話やショートメッセージの送信、個人情報の共有を求めることはありません。疑わしい行為を見つけたら「迷惑行為を報告」からご報告ください。

詳しく学ぶ
このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。
アーカイブに保管済み

what's the difference between Find and Quick Find?

cor-el replied
mkupper

Ctrl-F brings up the Find Bar which search all text on the page.

The "/" brings up the Quick Find bar which also seems to search all the text on the page.

What is the difference between Find and Quick Find? I can see that Quick Find is missing the additional options that Find has but is the search itself exactly the same? I can see how Quick Find (links-only) is different but can't see why FF has both.

Searching for this finds many pages from people on how to disable Quick Find, how to point it at Find, etc. Apparently Quick Find was introduced back in FF ver 2 upsetting many people that use the ' key on some of their sites. I could not find any pages that explained the difference between the two finders.

Ctrl-F brings up the Find Bar which search all text on the page. The "/" brings up the Quick Find bar which also seems to search all the text on the page. What is the difference between Find and Quick Find? I can see that Quick Find is missing the additional options that Find has but is the search itself exactly the same? I can see how Quick Find (links-only) is different but can't see why FF has both. Searching for this finds many pages from people on how to disable Quick Find, how to point it at Find, etc. Apparently Quick Find was introduced back in FF ver 2 upsetting many people that use the ' key on some of their sites. I could not find any pages that explained the difference between the two finders.

この投稿は mkupper により に変更されました

すべての返信 (1)

There is no difference between the two.
Only the buttons are missing on the Quick Find bar, so may not notice if Match case is selected and you can't click the Next and Previous buttons.
The Quick Find bar closes automatically after a few seconds (pref accessibility.typeaheadfind.timeout).