Hacker News Reader

Comment by cstrat | Hacker News Reader

I think I have seen this implemented before and when it inserts the extra 'oo' it automatically ignores extra 'o's that might be typed. It allows for users to actually type Google, but also allows users to type 'Ggle' and get the same response.

View on HN

The article mentions this being on some activation like tab or similar like bash uses. Automatic completion could work with two levels of highlighting. Example with []/{} showing active/suggestive:

  "[G]" <- Typed
  "[G]{oo}" <- Displayed in input, with Google/GoodReads as options
  "[Goo]" <- Tab Pressed
  "[GoodReads"] <- R Pressed
  "[Google"] <- g pressed
  "[Gx]" <- Any other character x

Then things like Chrome's url bar will fill in the complete first suggestion with a way to clear it which gives UX like:

  "[G]" <- Typed
  "[G]{oogle}" <- Displayed
  "[G]" <- Backspace pressed

Usually I've seen right arrow as the activation key.

That's horrible. What if you want to type 'Ggle'?

I think this type of Autocomplete only works on fixed lists. You're right, it would be completely annoying if it were a free text field with autocomplete suggestions...

Don't make me backspace twice when I want to type "Github" but it isn't in autocomplete yet.

This needs to special case when the next character that would break the ambiguity can also be an o.

Reply on news.ycombinator.com