That is keeping with google's newly found traditions. For example, the ajax-ing of search has mostly broken the back key among others.
Shit Case 1: sometimes you do a search, find a new phrase and begin typing it only to see the phrase disappear from the original search results and replaced with updated results for an incomplete and often incoherent query.
Shit Case 2: often I begin typing a new search query and realize mid "sentence" that the current query was fine. Well, too late. Because the results have already refreshed. Hitting the back key does little good. In best case, it doesn't work. In worst case, it will take you to the previous physical page that you were on before you came to google.
I find some of these changes mind boggling and can only convince myself to accept them by tell myself "hey google looks at the numbers, may be most folks just like it". Particularly the ajax search...annoys the crap out of me and finds way to enable itself even when I disable it.
> I find some of these changes mind boggling and can only convince myself to accept them by tell myself "hey google looks at the numbers, may be most folks just like it". Particularly the ajax search...annoys the crap out of me and finds way to enable itself even when I disable it.
Google needs to be usable by everyone. They iterate the product to make sure that most people get good search results. But this means that some people are getting sub-optimal results, especially as Google makes changes to the way search works.
Google didn't used to use stemming. Some words are now stemmed automatically. Google didn't used to substitute words. Some words are now substituted automatically. Google used to use + to force inclusion of a word, but they've dropped that and now use quotes to "force" "inclusion" of words "or phrases".
> In the past, we provided users with the “+” operator to help you search for specific terms. However, we found that users typed the “+” operator in less than half a percent of all searches, and two thirds of the time, it was used incorrectly.
Check my math, but I think that means that + was used correctly in only 1 out of 600 searches.
And how many millions of correct searches was that? How many millions of extra seconds are spent wrapping whole words in quotes rather than just a '+'? It could even be costing lifetimes!
I am one of those people that loves the AJAX search. I know it's generally hated around here but I think getting the suggested results as you type in your search is one of the best search features Google has implemented.
For example, let's say I found some new framework for a new language I haven't worked with. I can easily find competing frameworks by typing in something like '[framework name] vs' and Google will will suggest the most commonly compared frameworks. I think it's very useful when you don't know exactly what you are searching for. Yes, I know it has some usability issues but in my opinion the pros outweigh the cons.
You are talking about Suggestions which is an entirely different feature than auto-refreshing of search(though both use ajax so I could have used a better description in my OP). I personally love Suggests as much as you.
What I hate is when I type, say a few letters of my query, and begin seeing frivolous search results begin to appear. I hate when I hit the back key, often it takes me to the previous page or simply removes the last letter from my query and updates the results. I hate when I begin typing an obscure name I just found from another query and see it disappear after I have typed a couple of letters.
I was just fine hitting the "return" key to pull up search results.
BTW you can fix both of these issues by disabling Javascript for http?://www.google.com/search/* (I use the "site preferences" in Opera for this, but I assume other browsers have similar built-in features). What you get back is something very much like the old vanilla Google web search.
I used to have it for quite some time, new laptop set it back to normal, and for now it hasn't quite annoyed me enough yet to set it again (also because I'm using DuckDuckGo much more these days, for similar reasons), but it was good when I had it.
I really wish Google had some setting to turn off this "instant search update" thing, as well as how the input box continuously steals the focus (this breaks many keyboard shortcuts in Opera), because the other interactive/dynamic features they do with JS on the web search page are quite useful.
Google seems to be one of the prime culprits making web pages and browsers so complicated that functions useful for reading which used to work everywhere are now broken on a significant number of pages.
Parent mentions scrolling with the space key. Another: selecting text (prior to copying it). Another: making text bigger, e.g., with the Zoom In ("+") button. Another: going to the start or end of the page. Another: scrolling without annoying or time-wasting latency.
Besides the scrolling problem, the pinned header also pins down a low-value use for the easiest-to-read part of the page. That is, reading on a laptop you have a narrow screen set low, making you bend your neck to read the lower parts of the page, where all these jokers force the actual text you're trying to read.
