DOJO widgets with same data source display an error on get('value') when created programmatically
When creating two (or more) widgets programmatically that have the same source, for instance: two dijit.form.Select objects, they present a curious bug.

Code:

                 dojo.xhrPost({
                    url:"servletName",
                    content:{action:"getData"},
                    handleAs:"json", 
                    load:function(response,ioArgs){ 
                        var oneSelect = new dijit.form.Select({
                                  name: 'one',
                                  id:'one',
                                  options: response,
                                  }).placeAt(dojo.query("#oneDiv")[0]);`
    
                        var anotherSelect = new dijit.form.Select({
                                  name: 'two',
                                  id:'two',
                                  options: response,
                                  }).placeAt(dojo.query("#anotherDiv")[0]);
                        },
                        error:function(error,ioArgs){
                                //Error occurred!
                        }
                  });


(Let's say that the response is in this form:

    [{label:'x value',value:'x'},{label:'y value',value:'y'}]


so this would produce something (obviously not the result after creating the dijit programmatically, of course, but it's for clarifying purposes) like:

    <select dojoType...>
       <option value='x'>x value</option>
       <option value='y'>y value</option>
    </select>

Now, when doing a get value from those two dijits, even when they point to different options:

    dijit.byId('one').get('value'); //Gives x value!
    dijit.byId('two').get('value'); //Gives ALSO x value!

Anyone else gets that behavior too? Seems to me like a bug.
DOJO widgets with same data source display an error on get('value') when created programmatically
===

When creating two (or more) widgets programmatically that have the same source, for instance: two dijit.form.Select objects, they present a curious bug.

Code:

                 dojo.xhrPost({
                    url:"servletName",
                    content:{action:"getData"},
                    handleAs:"json", 
                    load:function(response,ioArgs){ 
                        var oneSelect = new dijit.form.Select({
                                  name: 'one',
                                  id:'one',
                                  options: response,
                                  }).placeAt(dojo.query("#oneDiv")[0]);`
    
                        var anotherSelect = new dijit.form.Select({
                                  name: 'two',
                                  id:'two',
                                  options: response,
                                  }).placeAt(dojo.query("#anotherDiv")[0]);
                        },
                        error:function(error,ioArgs){
                                //Error occurred!
                        }
                  });


(Let's say that the response is in this form:

    [{label:'x value',value:'x'},{label:'y value',value:'y'}]


so this would produce something (obviously not the result after creating the dijit programmatically, of course, but it's for clarifying purposes) like:

    <select dojoType...>
       <option value='x'>x value</option>
       <option value='y'>y value</option>
    </select>

Now, when doing a get value from those two dijits, even when they point to different options:

    dijit.byId('one').get('value'); //Gives x value!
    dijit.byId('two').get('value'); //Gives ALSO x value!

Anyone else gets that behavior too? Seems to me like a bug.