#3727 closed enhancement (wontfix)
FilteringSelect/ComboBox: should generate <select> elements on iphone
Reported by: | alex | Owned by: | haysmark |
---|---|---|---|
Priority: | low | Milestone: | 1.3 |
Component: | Dijit - Form | Version: | 0.9 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
we're not going to be able to beat the built-in UI for option selection on the iphone any time soon. Better to give a UI that works well and still be able to back it w/ a data set.
Change History (7)
comment:1 Changed 15 years ago by
Milestone: | 1.0 → 1.1 |
---|
comment:2 Changed 15 years ago by
Milestone: | 1.1 → 2.0 |
---|---|
Summary: | filtering select and combo box should generate <select> elements on iphone → FilteringSelect/ComboBox: should generate <select> elements on iphone |
Type: | defect → enhancement |
comment:3 Changed 15 years ago by
Owner: | changed from bill to haysmark |
---|
comment:4 Changed 15 years ago by
Ok Alex, if you send me an iphone I will develop on it. Otherwise no go.
comment:6 Changed 14 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:7 Changed 11 years ago by
Component: | Dijit → Dijit - Form |
---|
Note: See
TracTickets for help on using
tickets.
This doesn't sound possible in the general case since:
1) combobox let's you input any values whereas <select> does not
2) FilteringSelect? allows user input to query against a database whereas <select> does not
3) there are plans for a Select widget corresponding with normal <select> but allowing HTML. That would almost be possible to convert to a <select>, except for the HTML part.