[PR3] IDs not being set on numberfield fields?

[stefankendall]

It looks like IDs aren't being set on form elements that specify an ID.

This:

{
                    xtype:'fieldset',
                    defaults:{
                        labelWidth:'35%',
                        listeners:{
                            change:myChangeEvent
                        }
                    },
                    items:[
                        {
                            id:'myId',
                            xtype:'numberfield',
                            name:'myMax',
                            label:'MyLabel',
//                            disabled:true,
                            disabledCls:'disabledVisible'
                        }
                    ]
                }
}

produces this in the DOM:

<input class="x-input-el x-form-field x-input-number" type="number" id="ext-element-290" name="myMax">

Ext.getCmp('myId') seems to return an element, but Ext.getCmp('myId').getValue() only returns the initial value of the numberfield.

Somehow the DOM and the ext element are de-synced.

[mitchellsimoens]

1. id should only be used for debugging purposes. It isn't worth writing a system to have unique ids. Code for reusability
2. Using the following code, Ext.getCmp('myId') got the correct field. Ext.getCmp('myId').getValue() returned 0. I then typed 3 into the field and did the getValue() again and it returned 3 as expected. I cannot reproduce this error in PR3.

Ext.create('Ext.form.Panel', {
    fullscreen : true,
    items      : [
        {
            xtype:'fieldset',
            items:[
                {
                    id:'myId',
                    xtype:'numberfield',
                    name:'myMax',
                    label:'MyLabel',
                    disabledCls:'disabledVisible'
                }
            ]
        }
    ]
});

[stefankendall]

I'm using the IDs to drive automated testing. In 1.1.0 and 1.1.1, IDs were being assigned to elements on the DOM.

getValue and setValue also aren't working for me, so I'll try and create a full example on jsfiddle. I still think not creating actual IDs is an issue.

[mitchellsimoens]

I'm using the IDs to drive automated testing. In 1.1.0 and 1.1.1, IDs were being assigned to elements on the DOM.

getValue and setValue also aren't working for me, so I'll try and create a full example on jsfiddle. I still think not creating actual IDs is an issue.

An id is automatically created for components and are then used for their top level DOM element.

[robl]

So if Sencha Touch is automatically assigning IDs, then how do you suggest he do automated testing via say Selenium if the ids change each time the app is run?

[Jamie Avins]

Indeed if the id isn't being respected, this is a bug and needs to be handled properly. Assigning ids is a necessary feature.

[stefankendall]

I didn't have the root cause here of another issue. I'm going to close this and re-post; the IDs are being set properly.