[geeks] Google Irritation

[Shannon Hendrix]

On Feb 24, 2009, at 18:15 , Sridhar Ayengar wrote:

> Michael Parson wrote:
>>>> That's strange ... it'll tell me that I should really be  
>>>> searching for
>>>> what it thinks the word should be spelt as ("Did you mean: Color
>>>> bits" (bloody cheek ... that's a spelling issue in itself here)),  
>>>> but
>>>> goes ahead and searches for the "bad" spelling anyway. There didn't
>>>> seem to be any options to change this behaviour that I could see.
>>>
>>> Try searching for "atlast".  8-(
>> I did:
>> atlast -"at last"
>
> Anthony gave me a workable solution, but it would have been  
> thoroughly unacceptable to have been forced to use your suggestion.   
> If this was the only possible solution, in my mind, Google Search  
> could be labeled as broken.
>
> It's borderline counterintuitive garbage even taking into account  
> Anthony's solution.

Are sure that Google is doing all of this?

A lot of newer browsers do exactly what you are describing in editable  
fields, and it drives me crazy.

Of course, I think Google does overload simple text input with stupid  
JavaScript madness, so it could be an evil combination even.

It would be nice if you could selectively kill idiotic JS input mods  
for text fields on most sites.


-- 
Shannon Hendrix
shannon at widomaker.com