This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Rohkem teavet

find not working in firefox

  • 4 vastust
  • 21 on selline probleem
  • 2 views
  • Viimati vastas Dzynit

more options

In the last 2 days firefox updated auromatically. Current version is 24.0

When I select conmand F on Mac OS X. Usually the find box appears on the bottom left of the page. Which it does. Usually once I select command F I can then type a search term in the area automatically this is broken in the latest update. Even when I type in a search manually the find is still broken.

I use this feature a lot every and would not like to be forced to use chrome.

If anyone can help with a fix that would be great.

Thank you.

In the last 2 days firefox updated auromatically. Current version is 24.0 When I select conmand F on Mac OS X. Usually the find box appears on the bottom left of the page. Which it does. Usually once I select command F I can then type a search term in the area automatically this is broken in the latest update. Even when I type in a search manually the find is still broken. I use this feature a lot every and would not like to be forced to use chrome. If anyone can help with a fix that would be great. Thank you.

Valitud lahendus

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).

To Enable SafeMode

  • You can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
  • Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.
  • Once you get the pop-up, just select "'Start in Safe Mode"

If it works in Safe Mode and in normal mode with all extensions (Tools > Add-ons > Extensions) disabled then try to find which extension is causing it by enabling one extension at a time until the problem reappears.

Close and restart Firefox after each change via "Firefox > Exit" (Windows: Firefox/File > Exit; Mac: "Firefox > Quit Firefox"; Linux: "Firefox/File > Quit")

Loe vastust kontekstis 👍 0

All Replies (4)

more options

Valitud lahendus

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).

To Enable SafeMode

  • You can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
  • Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.
  • Once you get the pop-up, just select "'Start in Safe Mode"

If it works in Safe Mode and in normal mode with all extensions (Tools > Add-ons > Extensions) disabled then try to find which extension is causing it by enabling one extension at a time until the problem reappears.

Close and restart Firefox after each change via "Firefox > Exit" (Windows: Firefox/File > Exit; Mac: "Firefox > Quit Firefox"; Linux: "Firefox/File > Quit")

more options

Thank you for a quick reply.

It worked great. I should have known this myself.

My best wishes to you,

Ricardo

more options

I have this, but I'm tired of chasing problems and trying to work out "solutions" after almost every update of Firefox. Why mess with things that work? Firefox update release ought to work in the first friggin place or don't bother to update at all!... much disappointment.

Muudetud UFQuack poolt

more options

I had this problem too and it was only if I had facebook open in a tab. It turned out to be the facebook desktop plugin that was the cause. Thought I'd share this in case it might help someone else.