Opened 11 years ago

Closed 10 years ago

#4940 closed enhancement (wontfix)

ComboBox/FilteringSelect: autosize feature

Reported by: Adam Peller Owned by: Nathan Toone
Priority: high Milestone: future
Component: DojoX Form Version: 0.9
Keywords: Cc: haysmark, Douglas Hays
Blocked By: Blocking:

Description

would be particularly helpful for i18n, where the string sizes aren't always known

Change History (6)

comment:1 Changed 11 years ago by bill

Cc: Douglas Hays added
Milestone: 1.12.0
Owner: Douglas Hays deleted

It's not going to be realistic to size-to-fit FilteringSelect? or ComboBox? for the general case, since there may be millions of values and we don't want to pull them all in from the data store and put them into the DOM in a hidden way, nor do we want to do javascript sizing.

I realize there's a I18N issue, but this probably makes more sense to do for a select widget that doesn't involve dojo.data (#3270). Anyway, let's discuss when we have some time.

comment:2 Changed 11 years ago by alex

Milestone: 2.01.3

Milestone 2.0 deleted

comment:3 Changed 10 years ago by bill

Component: DijitDojoX Form
Milestone: 1.31.4
Owner: set to dante
Summary: FilteringSelect autosize featureDropDownSelect: autosize feature

Yah, my comment above stands. May be suitable for DropDownSelect? widget in dojox.form though so reassigning there.

comment:4 Changed 10 years ago by bill

Milestone: 1.4future
Owner: changed from dante to Nathan Toone

comment:5 Changed 10 years ago by Nathan Toone

I'm not quite sure what you mean here - but the dojox.form.DropDownSelect? is already auto-width...that is, it will be the width of whatever its value is.

comment:6 Changed 10 years ago by bill

Resolution: wontfix
Status: newclosed
Summary: DropDownSelect: autosize featureComboBox/FilteringSelect: autosize feature

OK, then going to mark this as wontfix (as per my original comment).

We could theoretically download all the data up front, render all of it in order to get width, and then hide the unwanted rows, but that's starting to sound like an entirely separate widget, one which wouldn't be suitable for the large amounts of data FilteringSelect is meant to deal with.

Note: See TracTickets for help on using tickets.