4 ms·

For the love of christ, whatever you do, please don't ever implement "DuckDuckGo Instant®". This auto-complete predictive suggestion list business isn't half b

For the love of christ, whatever you do, please don't ever implement "DuckDuckGo Instant®". This auto-complete predictive suggestion list business isn't half bad, but there's nothing I hate more about Google than their bloody "Instant" features.

coherentpony 12y ago
Nothing wrong with implementing it and giving users an option to turn it on or off. Immediate disregard seems a little harsh.
- Pacabel 12y ago
  Are you currently seeing that option somewhere? I looked in the settings, but I did not see it there, and I do not see any other way to disable that functionality.
  - coherentpony 12y ago
    Currently, no. My suggestion was to implement such an option.
cainetighe 12y ago
We were on the fence about autocomplete for a variety of reasons, but tried to be careful about minimizing distraction. It was too great a vector to introduce !bang autocomplete :). As always, please let us know what you think as it evolves!
jfoster 12y ago
Can you explain what you don't like about it? I was just thinking the (almost) opposite, that a full page reload after searching seems unnecessary.
- terminado 12y ago
  Google Instant is irritating because I'm trying to type a search string into a field in the middle of the page, and as soon as I enter a single keystroke, my entire thought process is interrupted when the field I'm focusing on is thrown upwards to the top of the page, without waiting for me to confirm that I'm finished typing. So I want to search for "apple" and guess what: I type the letter "a"... Now the whole page is disrupted, and I have to stop, and check the page, to make sure the sudden change is what I expected it to be. Is the page doing what I intended? I only typed one letter... Did I actually type the letter "a", or did my finger slip and type the letter "s"? Wait, where's the field? Oh, it's up at the top of the page now... What was I doing? Oh, right, I was going to search for "apple"... Why did the page change, when I wanted it to stay put, while I complete my thought? Why didn't the page wait until I pressed the enter key, to confirm that I was finished, and ready to search for the intended query? Do I care about whether the page sends an ordinary post with a form submission, and reloads the page? No. Do I care about whether the page sends an AJAX request, and is re-rendered by a JavaScript library? No. I want the page to remain static and reliable while I perform my task. After I'm done typing, it can go crazy, and do whatever.

coherentpony 12y ago

Nothing wrong with implementing it and giving users an option to turn it on or off. Immediate disregard seems a little harsh.

Pacabel 12y ago
Are you currently seeing that option somewhere? I looked in the settings, but I did not see it there, and I do not see any other way to disable that functionality.
- coherentpony 12y ago
  Currently, no. My suggestion was to implement such an option.

cainetighe 12y ago

We were on the fence about autocomplete for a variety of reasons, but tried to be careful about minimizing distraction. It was too great a vector to introduce !bang autocomplete :). As always, please let us know what you think as it evolves!

jfoster 12y ago

Can you explain what you don't like about it? I was just thinking the (almost) opposite, that a full page reload after searching seems unnecessary.

terminado 12y ago
Google Instant is irritating because I'm trying to type a search string into a field in the middle of the page, and as soon as I enter a single keystroke, my entire thought process is interrupted when the field I'm focusing on is thrown upwards to the top of the page, without waiting for me to confirm that I'm finished typing. So I want to search for "apple" and guess what: I type the letter "a"... Now the whole page is disrupted, and I have to stop, and check the page, to make sure the sudden change is what I expected it to be. Is the page doing what I intended? I only typed one letter... Did I actually type the letter "a", or did my finger slip and type the letter "s"? Wait, where's the field? Oh, it's up at the top of the page now... What was I doing? Oh, right, I was going to search for "apple"... Why did the page change, when I wanted it to stay put, while I complete my thought? Why didn't the page wait until I pressed the enter key, to confirm that I was finished, and ready to search for the intended query? Do I care about whether the page sends an ordinary post with a form submission, and reloads the page? No. Do I care about whether the page sends an AJAX request, and is re-rendered by a JavaScript library? No. I want the page to remain static and reliable while I perform my task. After I'm done typing, it can go crazy, and do whatever.