[CLOSED] [3.0rc1.1] ComboBox/JsonStore bug

This may or may not be fixed in the SVN tree, but since I don't have access to that I can neither confirm nor deny, and thus I am submitting this as a bug report.

Version: Ext JS Library 3.0 RC 1.1

Executive Overview:

I created a ComboBox with mode: remote and a JsonStore store.

When clicking the trigger the dropdown appears with the spinner and the "Loading..." text.

Using Firebug I can confirm that the remote data script was properly called, and returned the below quoted data.

Tracing through the Ext JS code I've found that the Ext.data.Store.loadRecords() call to this.fireEvent("datachanged", this) fails to call the registered 'datachanged' function Ext.DataView.refresh(). (This is registered in Ext.DataView.bindStore())

Inside the EXTUTIL.Observable.prototype.fireEvent call for 'datachanged' the 'ce' parameter is set to the boolean value of 'true' and NOT an object -- causing the ce.fire.apply(ce,a) call to be skipped.

The creation of my ComboBox:
I have two methods by which I've tried to create the ComboBox -- both exhibited the SAME behavior.

I'd suggest you add a loadexception listener to your store to make sure it's all working properly.

Twitter - @evantrimboli
Former Sencha framework engineer, available for consulting.
As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.

I'm using the latest SVN build. However I'm reasonably sure xtype support for stores in combos was added post RC1.1. Try your code using a pre-declared store instead of using an xtype.

Twitter - @evantrimboli
Former Sencha framework engineer, available for consulting.
As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.

There was a bug in the combo that if you provided an xtype store it would end up creating 2 store objects, so the dataview would have a seperate store to the combo.

Twitter - @evantrimboli
Former Sencha framework engineer, available for consulting.
As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.

Well, now that you put it that way -- apparently I hadn't tried that specific permutation. That fixed my problem. I'll comment my code to try the xtype method when you release the next RC or the final 3.0