Opened 14 years ago
Last modified 14 months ago
#15881 new Cleanup/optimization
FilteredSelectMultiple does not respect order
Reported by: | bmihelac | Owned by: | nobody |
---|---|---|---|
Component: | contrib.admin | Version: | 1.3 |
Severity: | Normal | Keywords: | javascript |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | yes |
Description
WIth filter_horizontal and filter_vertical admin options moving items between available and chosen, these items would be moved to the end of respecting lists.
I believe it would be useful and not so hard to preserve original sort order.
Change History (3)
comment:1 by , 14 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 13 years ago
UI/UX: | set |
---|
comment:3 by , 9 years ago
Note:
See TracTickets
for help on using tickets.
It also does not respect the order of the selected choices when the form is reloaded.
I am using a comma-separated-value-list custom field, which stores choices id in the form of a string (ex: '12,66,13').
When retrieved from the database, this field is converted into a list using the split method. The example above would be converted to [12, 66, 13].
The first time you create the object with a new form, you can select choices one by one, and their order is kept in the resulting list (because they are added one by one in the widget right/bottom part by the javascript function). But when you save it and reload the page, the order is no longer maintained since it is lost while rendering the HTML. The selected part is now ordered the same way the available choices are. Indeed the javascript code just iterate over the "options" of the available part and add them in the chosen part if it encounters the "selected" attribute.
The simplest solution I could think of to solve this is to add another attribute or class to the HTML "option" elements with the index of the selected choice as value, and use this new value in the javascript code to move them in the chosen part according to it.
Workaround
Python code in django.contrib.admin.widgets.Select.render_option
This would also require to have a list instead of a set (in render_options), because set are unordered:
Generated HTML
JavaScript code in SelectBox.js
This is just a proposition, I didn't test it yet, but I'll post some results when I do.