When typing in an input field where the jQuery UI Autocomplete component is active, characters have a tendancy to get deleted when autocompletion kicks in.

I think this is best explained through an example case:
User types "@Phone" in the Context field of the new action form.
Along the way, say, when the user has typed in the characters "@Pho", the autocompletion JS seems to kick in, adding the class "ui-autocomplete-loading" to the active input element. This class is soon removed, and if a suitable candidate was found in the autocomplete source array it is shown as a suggestion under the active input element. However, in that case, if the user entered any new characters in said input field in the brief period the "ui-autocomplete-loading" class was active, those characters are removed from the field. (This almost looks to be an intentional way for the JS to ensure the integrity of the autocomplete suggestion).
Thus, when the user is finished typing, the input field might read "@Phoe" instead of "@Phone" as the user intended. Ofcourse this is when the autocomplete JS kicks in again, finds out that "@Phoe" doesn't match anything in the source array, and removes the suggestion.

This is annoying as hell. Autocompletion is king, but it should not interfere if I want to spell something out myself. That is often quicker anyway.

The sad thing is that from what I have gathered this doesn't seem to be "Tracks' fault". More likely this is either a necessary consequence of the inner workings of jQuery UI Autocomplete, or a poor thought out feature.

Maybe we should ask the jQuery UI team?


Confirmed on Firefox 3.6.15/Linux, Firefox 4.0/Linux, Firefox 3.5.8/OSX, Opera 11.01/OSX and Safari 5.0.1/OSX.