I haven't, but when one is available then you'll be able to find it at userscripts.org (us.o) I'm sure. If you look at the us.o page for the 'google' tag (which is sorted by 'last updated by default) you should find all of the scripts that update the Google search engine page results (SERP), and there is a Google group on us.o where ppl can maintain a collection of Google related userscripts and discuss Google userscripts.
If you can't find the userscript that does what you want and works, then you can either start a discuss with an author of a script that doesn't work, tag the userscript as having an issue and describe the issue, request someone make a userscript that does what you want here, or get help making a userscript your self here and/or here.
To work around the issue, you can use the parameter complete=0
in the Google address to turn off Google's autocomplete.
In Opera, for example, you can make a bookmark to http://www.google.com/?complete=0
with nickname google. You can then go to the address box, type google, and press Enter to start a Google search session with autocomplete off.
Or you can go to Tools → Preferences → Search, edit the Google entry and add &complete=0
to the end of the address. Then the Google selection in Opera's search box will use Google with autocomplete off.
Test steps
I'm using Windows XP and Opera 10.1. I went to Google → Search Settings and turned off Google Instant.
I went to http://www.google.com/search?q=THIS+IS+VERY+UNIQUE+SEARCH+QUERY. When I clicked in the search box on the page and typed a letter, I could see the progress bar quickly flash in the address box indicating something was loaded. It seems that if I'm still holding a keyboard key down when the progress bar disappears, then the text cursor moves to the end of the search box.
If I go to
http://www.google.com/search?q=THIS+IS+VERY+UNIQUE+SEARCH+QUERY&complete=0 then the bug no longer happens.
Best Answer
NoScript's base functionality works domain-by-domain, but the Application Boundaries Enforcer (ABE) can work on specific URLs and it's flexible enough to do what you want.
Here's the USER rule I used to get decent searching without breaking the rest:
Just add it at the end in
NoScript Options > Advanced > ABE > User
.The
Site
line matches both the page you load and the URL used under the hood for Google Instant updates, so whether the combination ofSite
andINC()
matches on the URL of the top-level request or the request being judged (NoScript's ABE docs aren't clear on this), it'll cause requests for new results without pressing Enter to fail.The
SCRIPT
in theINC()
may or may not ever get fired (see my comment about the lack of detail in the ABE docs) but, if it does, it explicitly blocks any external Javascript they may be pulling in.Finally, the
Sandbox
line tells ABE to allow the request for the page itself... but to do it with Javascript disabled. It and theSite
line may be the only ones you need, but I thought I'd play it safe.If you want more details, the aforementioned docs are at http://noscript.net/abe/abe_rules.pdf