[patch] [cla] bug in dijit/form/_AutoCompleterMixin

[Martin Repta]

We found that dijit.form.FilteringSelect? is not working correctly and probably all other widgets that inherits from dijit/form/_AutoCompleterMixin.

In out sample, we have filteringSelect with store which contains data with item where id == 0. When you try to select item with id == 0, the value of filteringSelect will be empty string.

Problem is inside condition, where _AutoCompleterMixin checks if value is not null. But this condision returns true also when value is 0.

I have attached sample to demostrate problem and also patch file.

[ben hockey]

technically this is not a bug since values are supposed to be strings

_setValueAttr: function(/*String*/ value, /*Boolean?*/ priorityChange, /*String?*/ displayedValue, /*item?*/ item){

if you change your ids to be strings then "0" will be handled properly.

i'll leave this open for doug or bill to decide what to do with it but i've seen a number of issues closed because values are integers rather than strings. i think its quite common that people don't realize that values have to be strings and personally, i'd like to see integers be valid values, but for now they're not.

[Martin Repta]

I think it is a bug, because it can accept integer values, but not 0, because condition if(!value) is not enough!

[Douglas Hays]

In [27621]:

Fixes #14644. Explicitly check for null/undefined to avoid integer 0 value failure.