jay@moduscreate.com
17 Apr 2011, 6:01 AM
This bug has plagued the framework since around .97 and I'm surprised it has not been caught. At first I thought it was me, but working on Sencha Touch in Action, I finally narrowed down the behavior pattern.
Looking at the code below, configuring a select field WITH a name, everything works as expected. However, without a name, it seems that tap even does not function, thus the select does not show.
var buildSelectField = function(label) {
return new Ext.form.Select({
label : label,
// name : label,
options : [
{
text : 'TOP',
value : 't'
},
{
text : 'BOTTOM',
value : 'b'
}
],
listeners: {
change : function(field, value) {
var values = selectFormPanel.getValues();
console.log(values);
}
}
});
};
new Ext.Panel({
fullscreen : true,
bodyStyle : 'padding: 10px;',
items : [
buildSelectField('_1'),
buildSelectField('_2'),
buildSelectField('_3'),
buildSelectField('_4')
]
});
NOTE :: The picker field works PERFECTLY without a name property inside of Webkit for the desktop AND the iPad, however for the iPhone:
http://tdg-i.com/img/screencasts/2011-04-17_1000.png
Looking at the code below, configuring a select field WITH a name, everything works as expected. However, without a name, it seems that tap even does not function, thus the select does not show.
var buildSelectField = function(label) {
return new Ext.form.Select({
label : label,
// name : label,
options : [
{
text : 'TOP',
value : 't'
},
{
text : 'BOTTOM',
value : 'b'
}
],
listeners: {
change : function(field, value) {
var values = selectFormPanel.getValues();
console.log(values);
}
}
});
};
new Ext.Panel({
fullscreen : true,
bodyStyle : 'padding: 10px;',
items : [
buildSelectField('_1'),
buildSelectField('_2'),
buildSelectField('_3'),
buildSelectField('_4')
]
});
NOTE :: The picker field works PERFECTLY without a name property inside of Webkit for the desktop AND the iPad, however for the iPhone:
http://tdg-i.com/img/screencasts/2011-04-17_1000.png