ComboBox Unusable if you use queryExpr: '*${0}*'

[George Sexton]

The combo box highlight algorithm is really messed up if you use the query expression * ${0}* Create a combo box with these elements:

<label for=IDLocationName>Name</label></th><td> <select data-dojo-props="queryExpr: '*${0}*'" data-dojo-type="dijit/form/ComboBox" id="IDLocationName" name="location_name" value="" > <option value="2">Bluebird Theater <option value="7">Mile High Stadium <option value="3">Ogden Theater <option value="8">Paramount Theater <option value="9">Red Rocks Amphitheatre <option value="10">The Crossing Church <option value="1">The Pepsi Center </select> Type: R (pause) e (pause) d Expected behavior: "Red Rocks" should be selected. Observed behavior: The combo box contains "Bed"

Type "The" (now pause) and type "P" Notice that you get "Blu P", not "The Pepsi Center" as expected.

I've got a sample page at:

​http://www.mhsoftware.com/caldemo/ComboBoxDemo.html

that demonstrates this.

[George Sexton]

I'm not really sure this is valid. I set the property for autoComplete=false, and I'm getting much more of what I expect. If you agree, please let me know how I could submit my code as an example.

[Douglas Hays]

The highlighting is done in a plain INPUT box. It's beyond the ability of the INPUT box to have more than 1 highlighted area. When you use contains, then you can have many unmatched areas, so autocomplete=false has to be used with contains.

[George Sexton]

How would I submit a documentation update for the API docs so that queryExpr clearly documents this?

[bill]

Thanks, it would be a pull request, see ​https://github.com/dojo/dijit/blob/master/CONTRIBUTING.md for details.