Autocompletion starting with Uppercase Letter

[bodinsamuel]

When the dalatist present some word starting by an upper case letter, the user type in lowercase and complete it with tab, the first letter will not be changed but the rest of the word is still well completed (I mean with upper case)

ie:
data given = Coca-Cola
data typed = co

user do tab

data displayed = coca-Cola

Don't know if it's a real issue but it's a bit annoying. Doesn't occur with other shortcut.

[jharding]

That's the expected behavior. Pressing tab to complete the query and selecting a suggestion from the dropdown, while resulting in similar outcomes, are 2 different actions. For the former you are completing your query based on the hint and for the latter, you are explicitly selecting a suggestion to be your query.

If others think this behavior is strange, I'm willing to consider changing it, but for now I'm inclined to leave it as is.

[fkammer]

In my opinion both action should have the same result. Autocomplete suggests the first dropdown item as hint so it would be nice, if pressing tab has the same result as choosing the item from the dropdown list.

[bodinsamuel]

@jharding It the way you explain it's perfectly logic, and a great option for users, but some may want to be same result.
That's why I don't consider it an issue but just a missing feature :)

[fkammer]

What about adding some preferences so the user can set an individual function for these actions?
Like this:

$('input.twitter-search').typeahead({
  data: [{
      name: 'accounts',
      prefetch: 'https://twitter.com/network.json',
      remote: 'https://twitter.com/accounts?q=%QUERY'
    },
    {
      name: 'trends',
      prefetch: 'https://twitter.com/trends.json'
    }
  ],
  onTab: function() {
    // action performed on tab
    // e.g. open the link given by the first object in dropdown
  },
  onClick: function() {
    // action performed when user clicks on a dropdown item
  }
});

If onTab and onClick isn't set the default function is used and it behaves like it do now.

Of course this would be a feature for the next major release, but in my opinion it would make typeahead.js more flexible and I think it would make it easier for you to add some features that should be optional like turning of autocomplete.