PDA

View Full Version : ComboBox Config Option: editable is not completely correct



akannu
12 Dec 2007, 10:30 AM
As per API documentation, the following is the definition:
----------
editable : Boolean ComboBox
False to prevent the user from typing text directly into the field, just like a traditional select (defaults to true)
----------

The part I disagree with is "just like a traditional select". A traditional select element in HTML allows user to type the 1st character directly into the field, but uses that entry to match.

The reason I am asking is..EXT has a combobox but not drop down (similar to SELECT). Actually, we like the flexibility and config options of combobox. At the same time, we want to know if there is anyway we can make it work just like a SELECT/DROP DOWN if we ever come across a need for it.

fay
12 Dec 2007, 1:57 PM
Have you looked at: Ext.form.SelectBox (Make a ComboBox work behave like an HTML SELECT) (http://extjs.com/forum/showthread.php?t=6392)

akannu
21 Dec 2007, 7:31 AM
Hi Fay
Thanks for referring to the other thread. The User Extension SelectBox does seem to solve what we are looking for (i.e. matching user input with 1st character and auto selecting). However, not everyone can use user extension due to licensing issues.

I think in addition to COMBO BOX, Ext should provide the following controls:

1) DROP DOWN (Ext Widget for SELECT HTML element)
2) LIST (Ext Widget for SELECT HTML element with Multiple attribute)

with each having their own config options.

This would allow for flexibility and let everyone use what is best for them.

I still contend that the assumption HTML select does not allow typing is wrong. It does support keyboard typing, but use it for matching of 1st character amongst the drop down entries.

tryanDLS
21 Dec 2007, 10:40 AM
@akannu - You're certainly free to suggest those things in a Feature Request - however they are not bugs. Even if those items were to added to the list of new functionality, it would be in 2.0 - at this point the 1.x codebase is not likely to get new functionality unless it can very easily be backported from 2.0.