Cobalt Edge

Example:
- you type "Portland"
- the request is like /getCities?q=portland
- the server gives back something like:
[{id: 123, value : 'Portland, Oregon'}, {id:456, value: 'Portland, Maine'}]
- if you set mustMatch:true the ac-script creates a new request after selecting id 456:
/getCities?q=portland,+maine
- this will likely be empty

You would have to fix or override the 'hideResultsNow' method

The problem is the 'multiple' option. When set to true the comma should act as a separator causing whatever you type on either side of the comma to be sent back as an option. The problem is that if you look at the autocomplete source code you will notice that all of the spots in the code check to make sure the multiple:true option is in use before splitting the code. All that is except one spot.

In function trimWords you will see no check to make sure multiple:true is enabled before it just goes ahead and trims the words.

To correct this replace this:

function trimWords(value) {
if ( !value ) {
return [""];
}
var words = value.split( options.multipleSeparator );

var result = [];
$.each(words, function(i, value) {
if ( $.trim(value) )
result[i] = $.trim(value);
});
return result;
}

WITH THIS:

function trimWords(value) {
if ( !value ) {
return [""];
}
var words
if (options.multiple) {
words = value.split( options.multipleSeparator );
}
else{
words[0] = value
}
var result = [];
$.each(words, function(i, value) {
if ( $.trim(value) )
result[i] = $.trim(value);
});
return result;
}

Notice the else part that loads the single value into the array. This could easily be written to just return the trimmed value right there but doing it this way works just as well and makes it easy to make see what is happening.

I have oddly not had issues with dashes but... who knows....

Hope this helps!!!