i tested this with ext3.0.3 and 3.1.0. in my example i have 4 users, 3 named john. onSelect i show the selected id in the console (correct!). when pushing the form.submit()-button, the form submitts always the id of the first "john" (2), even if 3 or 4 was selected before. therefore click at the sent params (post) and look at the value of the user.

so the this.value == rec.get(this.valueField) part will fail, because in rec is the first rec with the matching displayField !!

Please do test. I have adopted a large project written in ExtJS and I keep hitting with my head into the wall all the time fixing bugs...

teqneers

30 Aug 2010, 11:22 PM

I second that - the bug still exists in 3.2.1 and as far as I've seen in 3.2.2 as well.

Actually I don't know why assertValue() is called on non-editable, forced-selection comboboxes at all. I doesn't make sense to check the value that only could have been set by clicking one of the options provided. In those cases (non-editable, forced-selection) we simply override beforeBlur with an Ext.emptyFn to ensure that assertValue() isn't called.

The [FIXED]-tag should be removed from this thread...

Best regards

Stefan

Condor

30 Aug 2010, 11:45 PM

There already is a new report #1033 (http://www.sencha.com/forum/showthread.php?101123-OPEN-1033-ComboBox-reports-incorrect-value-when-non-unique-display-fields-are-used&p=475694#post475694) for this issue (with suggested fix).

teqneers

30 Aug 2010, 11:50 PM

Thanks Condor... I should have invested some more time in searching.

It's quite hard to keep track of the issues and bugs in this forum-like issue tracker ;-)