slaton
Posts: 63
Joined: 9/27/2005 Status: offline
|
I think the Ajax autocomplete feature is inevitable given the way it has become ubiquitous elsewhere. But the current implementation doesn't seem quite right. If I'm typing very fast, which is most of the time, it's really common for me to unwittingly end up with the first thing on the list selected and searched, when what I really wanted was to type my own query and not be bothered. For me, Google's implementation of this is far less disruptive. I just went and compared them and here's the difference I see. In CellarTracker, you have to click on the search field to enter a query there. Quite typically, I let go of the mouse at this point and it ends up lurking somewhere just under this field. When I start typing and CT generates a list of queries, it notices that the mouse is within this query window and picks the closest entry as select now by default. This is despite the fact that I haven't actually moved the mouse since I started typing. It also means that if I press return on my own search query, it will get overwritten with the one CT has now selected from this list based on my mouse proximity. In Google, when I start typing a search query the search engine ignores the position of my mouse and no suggested query gets auto-selected by default. Its only if I then nudge or move the mouse that Google reads its location and selects the nearest query accordingly. My suggestion would be to change CT's behavior here to that of Google, and only pay attention to the mouse location if it is moved after the start of the entry of a search query.
|