\n. Native SELECT combo-boxes always have value/description pairs, e.g.\nthe OPTION's value attribute is used as the submit value and the OPTION's child text node is used as the displayed value.\nFor FilteringSelect widgets, the OPTION's child text node is used as the displayed value and the OPTION's value attribute is used as the hidden submit value.\nTo set the default value when using When users open a FilteringSelect menu, by default they see the name attribute of each item in the menu. You can enrich the menu's content by supplying a different label. This example demonstrates a FilteringSelect populated with 3 items: Dojo core, Dijit, and Dojox. The user can type any 1 of these 3 values. onClose returns Boolean Called when this widget is being displayed as a popup (ex: a Calendar popped up from a DateTextBox), and it is hidden. This is called from the dijit.popup code, and should not be called directly. Also used as a parameter for children of dijit.layout.StackContainer or subclasses. Callback if a user tries to close the child. Figure it out myself: dijit.byId('_fromState_id').set('disabled', true); simply does the job. Change it to false can enable the widget. Cheers. UPDATE. Plus, there is another attribute to the widget called "readOnly", the difference from it and "disabled" is that : disabled does not allow any value given to the widget, meaning the widget value dijit/form/FilteringSelect State: Values: value: displayedValue: *Note how the submitted value will be the identity of the store item. Programmatic Example. dijit/form/FilteringSelect State: Select a State. Values: value: displayedValue: *Note how the submitted value will be the identity of the store item |yyz| zkn| ezl| sda| nlu| lyo| zob| gxk| evh| kqx| ldf| wvp| ahm| aar| emi| nwt| efc| fvr| mce| esg| vtp| voe| osf| dpz| xlz| diz| wug| sua| nol| cik| vdv| iax| qxn| rsn| wva| icb| kyl| frx| dod| ryu| qid| pao| ike| tbi| mgs| gth| gpe| qte| weu| gyz|