Google instant is a cool idea, as it helps you to find what you are looking for
if you are not certain of the search term.
However, I've found that it actually slows down my use of Google, as it is
constantly anticipating my next input.
List the steps to recreate the problem.
1.Take the case where I actually know what search term I want to use, but I
typo'ed the input. Instant is trying to figure out what to do with my
corrections
2. Example: quote" a fish rts from the head"
3. Try to correct to: quote "a fish rots from the head"
Instant is actually interfering with my ability to fix this typo, as it is
trying to figure out what I mean while I'm typing. My browser input is actually
slower because of Instant.
The solution: apply something like the Nagle algorithm to Instant. Don't
anticipate my input until I've stopped typing for a period of time. 500ms is
what TCP/IP uses, maybe that would be a good starting point. Most people who
know how to type type faster than 1 character per 0.5 seconds. Only do the
instant typeahead search after the user pauses for a brief period of time.
What version are you using?
OS=Linux, Fedore Core 8
Browser=Firefox 3.05
email: no6@pobox.com
Thank you for your attention.
Original issue reported on code.google.com by good4...@yahoo.com on 11 Sep 2010 at 7:17
Original issue reported on code.google.com by
good4...@yahoo.com
on 11 Sep 2010 at 7:17