Please, please, please change this feature.

myself and seemingly most others do not want an add-on or some option to disable this ” feature ” ..we just want to know how to delete it, remove it, get rid of it entirely

adding the searchkeys.disable.all and setting to true works in -some- areas.. google search and the firefox address bar, for example, but it does not stay disabled while typing in various forums.. the quick fix of resizing the firefox window is a decent work-around.. but why is there a need for a workaround… of a feature?

as of firefox 3.5.4 this is still a problem.. with no way to remove it

in summation, please don’t tell me to add some string to disable this, please don’t tell me to check/uncheck some search box.. just tell me how to delete it.

1. Type about:config in the address bar, and press enter.

2. Right click “Preference Name” and select New, then Boolean.

3. Type in “searchkeys.disable.all”. Press Okay.

4.Select “True”. Now you’re done!

The “Quick Find” feature should now be disabled

By the way, is it possible that whoever runs this site could put this info up at the top of the page? I passed over this site three times, thinking it only applied to firefox 2 (How could I have passed over it? I’m using 3.1, and at that point, my quick find buttons weren’t working correctly!)

Firefox 3 quick find can be repaired with
/* Add Next/Previous Buttons to Quick Find Bar */
.findbar-container>* {display: -moz-box !important;}
in the userChrome.css . This repairs quick find in Firefox 3.

/* Add Next/Previous Buttons to Quick Find Bar */
.findbar-container>* {display: -moz-box !important;}

instead.”

I added the line at the very end of the examplefile and renamed it….thats it!

I did find a “secret” command which disables it, but it came back after the next major update and I lost the command. ARGH!

Given that -F does the job, this running battle strikes me as similar to the religious wars between vi and EMACS users. (vi is an ancient unix editor with “modes” where clear keystrokes were sometimes commands based on which mode you were in. Emacs, on the other hand used the ESC, CTRL, and ALT keys to send commands to the editor.) I have always been an adherent to Emacs and the idea of a keystroke operating differently based on “focus” is not really all that appealing even if it did work.

I also have problems using copy and paste with firefox and I am suspicious that this is due to the same problem with focus.

My only add-ons are TabMixPlus and Firebug.

I saw the link to this post in feedback on support.mozilla.com, thanks for letting us know this exists, and of course we’re sorry this issue is still occurring.

A few things to start with: there have been several different causes for this issue and *most* of them have been fixed. This has been a very tricky issue to diagnose though, as the devs aren’t hitting it, and no one who does see this issue has yet been able to provide the clue needed to track this down.

It seems that the only reports left of this issue are from Mac users, or at least the majority anyway. What we need to diagnose this issue are people to get together who are seeing this issue to compare when it’s happening, and what sort of systems it’s happening on. Are you all using the same version of OSX? Do you all have the same extensions, or have some 3rd party software in common?

https://bugzilla.mozilla.org/show_bug.cgi?id=320465 is a tracking bug for all bugs filed to do with the quickfind bar coming up when it’s unwanted. If you look at the depends on section, any numbers that don’t have a line through them are still open. Note, it looks like a lot, but we make a practice of not resolving bugs fixed if the original reporter doesn’t come back and tell us it works for them. It looks like some of those bugs should be fixed, and some of them are duplicates of each other.

If you want to help, you could try to find a bug that looks like it’s *exactly* what’s happening to you, including your operating system and when it’s happening, and see if you can come up with any new information to add.

Please feel free to use a forum thread at http://support.mozilla.com/forum to coordinate with other users who are having this problem until you can find something in common. In fact that would be the preferable first step.

Next step would be to back up your profile and install a Firefox 3 beta from http://developer.mozilla.org/en/docs/Firefox_3_for_developers . Let us know if the problem still happens to you using those builds. If not, that will be a clue as well.

:) Ok, ok…My apologies. You are trying to help and I’m being flippant. But to make it perfectly clear, I DO have my cursor in a text field, such as this one (or for instance on MySpace or Google search) and the apostrophe will NOT work 99% of the time. There is that 1% miracle occurance when it does and it’s totally random. And, again, I DO have the “find text” option OFF in my preferences.

So, I will take your advice and contact Mozilla support and perhaps rather than re-explain the problem, I’ll simply direct them to this thread. I don’t think the point could be made any clearer.

If QuickFind appears even when on a text box then you should contact Firefox support (knowledge base, forums and now even live chat). It could be a conflict with an extension: http://support.mozilla.com

Thanks.

The other strange thing is that when it occurs when I’m in a google search text field, I’ll try three or four times to type with an apostrophe because all of a sudden it lets do it.

MOZILLA/FF: WAKE THE HELL UP!!! NO ONE LIKES YOUR “FIND” “Quick key” It’s LAME and USELESS! What? You think everyone on the internet is 1) illiterate and doesn’t know what contractions are or 2) so stiffly and properly articulate that they refuse to use them?? NO! We are a world of contractions! You’ve bungled it! AAAAAGGGGGHHHHHHHH!!!!! * runs off screaming, flailing arms *