საიტის გასაუმჯობესებელი სამუშაოების მიმდინარეობისას, შესაძლებლობების ნაწილი შეიზღუდება. თუ სტატიით ვერ მოახერხებ ხარვეზის გამოსწორება და შეკითხვის დასმა გსურთ, ჩვენი მხარდაჭერის გუნდი დაგეხმარებათ @FirefoxSupport გვერდის მეშვეობით Twitter-ზე და /r/firefox განყოფილებაში Reddit-ზე.

ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

Quick search issue

  • 2 პასუხი
  • 1 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 11 ნახვა
  • ბოლოს გამოეხმაურა koalamotorsport

OK, so for years of using Firefox, I was able to hit the / key, then start typing and it would search the page for whatever I was typing. Loved that feature.

Now, I don't need the / first. I just start typing and it automatically opens the quick search bar and starts jumping me around the page.

I looked here in the support section and there is no mention of a change. In fact, the instructions for quick search describe exactly how it used to be.

So, I'm confused. Has there been a change in Firefox, or am I experiencing some form of supernatural occurrence? I am running the latest version of Windows 10.

If this is a new change, can I turn it off? I'm using a piece of shit HP laptop and this new behaviour in Firefox is causing me all sorts of issues. Thanks Brett

OK, so for years of using Firefox, I was able to hit the / key, then start typing and it would search the page for whatever I was typing. Loved that feature. Now, I don't need the / first. I just start typing and it automatically opens the quick search bar and starts jumping me around the page. I looked here in the support section and there is no mention of a change. In fact, the instructions for quick search describe exactly how it used to be. So, I'm confused. Has there been a change in Firefox, or am I experiencing some form of supernatural occurrence? I am running the latest version of Windows 10. If this is a new change, can I turn it off? I'm using a piece of shit HP laptop and this new behaviour in Firefox is causing me all sorts of issues. Thanks Brett

გადაწყვეტა შერჩეულია

Hi Brett, could you check this setting:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(2) In the search box above the list, type or paste find and pause while the list is filtered

(3) If the accessibility.typeaheadfind preference is bolded and "modified" or "user set" to true, double-click it to restore the default value of false

Alternately, you can find it on the Options/Preferences page:

  • Windows: "3-bar" menu button (or Tools menu) > Options
  • Mac: "3-bar" menu button (or Firefox menu) > Preferences
  • Linux: "3-bar" menu button (or Edit menu) > Preferences
  • Any system: type or paste about:preferences into the address bar and press Enter/Return to load it

Scroll down to the Browsing section and uncheck the box for "Search for text when you start typing"

პასუხის ნახვა სრულად 👍 1

ყველა პასუხი (2)

შერჩეული გადაწყვეტა

Hi Brett, could you check this setting:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(2) In the search box above the list, type or paste find and pause while the list is filtered

(3) If the accessibility.typeaheadfind preference is bolded and "modified" or "user set" to true, double-click it to restore the default value of false

Alternately, you can find it on the Options/Preferences page:

  • Windows: "3-bar" menu button (or Tools menu) > Options
  • Mac: "3-bar" menu button (or Firefox menu) > Preferences
  • Linux: "3-bar" menu button (or Edit menu) > Preferences
  • Any system: type or paste about:preferences into the address bar and press Enter/Return to load it

Scroll down to the Browsing section and uncheck the box for "Search for text when you start typing"

Thanks Jscher2000, that was exactly it. accessibility.typeaheadfind was bolded and marked as modified.

No idea how that happened, but soooo glad it's fixed. You are my hero!