为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

what's the difference between Find and Quick Find?

  • 1 个回答
  • 3 人有此问题
  • 2 次查看
  • 最后回复者为 cor-el

more options

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)

more options

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