Opened 6 years ago
Last modified 3 years ago
#13019 reopened enhancement
Make dropdowns searchable / filterable
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases |
| Component: | web frontend | Version: | |
| Severity: | normal | Keywords: | css chosen |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Copied from 10012#comment:82:
About select boxes:
Another interesting library I recently discovered is http://harvesthq.github.com/chosen/ …
Wow, impressive! Yes, looks like it's a must have.
Any arguments against including it in core?
Not from my side. [cboos]
This would be especially useful for milestone selection. Often there are many milestones and finding a certain milestone can be difficult because they are sorted by due date. Allowing to use the filtering of chosen would be very helpful and nice.
Attachments (3)
Change History (15)
comment:1 by , 6 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
by , 6 years ago
| Attachment: | add_chosen_v1.8.5.patch added |
|---|
by , 6 years ago
| Attachment: | use_chosen.patch added |
|---|
by , 6 years ago
| Attachment: | chosen_milestone.png added |
|---|
follow-up: 8 comment:2 by , 6 years ago
Sorry, I thought it would be better a new ticket for attaching patches.
comment:3 by , 6 years ago
Instead of sorting the milestones alphabetically, filtering with Chosen can help for finding certain milestone or other field among many.
comment:4 by , 6 years ago
At least, the Chosen jquery plugin doesn't correctly work with Input_method (tested Chosen's demo on my Windows 10 for Japanese locale).
follow-up: 7 comment:5 by , 6 years ago
Also, you can create Trac plugin to apply Chosen jquery plugin rather than change Trac core.
comment:7 by , 6 years ago
Replying to Jun Omae:
Also, you can create Trac plugin to apply Chosen jquery plugun rather than change Trac core.
Alright. I thought it was maybe desired in Trac core:
Replying to Remy Blank:
Replying to cboos:
Replying to lkraav <leho@…>:
Any arguments against including it in core?
Not from my side.
Not from mine either, it definitely looks nice.
follow-up: 9 comment:8 by , 6 years ago
Replying to anonymous:
Sorry, I thought it would be better a new ticket for attaching patches.
I misunderstood. The ticket is not related to #2130.
select2 is another possibility that I've experimented yet. I think we should add the feature to the Trac core, but I don't want to do piecemeal changes of the user interface. It should instead be done as part of a user-interface facelift. If you don't want to wait for us to get around to that, the plugin is a good route to getting the feature in your Trac instance soon. See also #10012, MultiSelectFieldPlugin.
I don't want to discourage contributions, but the fact is that the TracTeam needs to put a considerable amount of effort to adopt changes like this. Currently we are focused on other things in our limited time. We'd welcome contributions on less-extensive changes though (see bitesized tickets).
comment:9 by , 6 years ago
| Keywords: | css chosen added |
|---|---|
| Resolution: | duplicate |
| Status: | closed → reopened |
Replying to Ryan J Ollos:
I misunderstood. The ticket is not related to #2130.
So not a duplicate of that ticket → reopening.
comment:10 by , 5 years ago
Similar request in th:ticket:13529 pointing to https://github.com/jun66j5/tracselectboxplugin using select2.
comment:11 by , 3 years ago
The use case described can be performed using one of the following plugins:
This ticket is also referenced by #918.
comment:12 by , 3 years ago
| Milestone: | → next-major-releases |
|---|
Please comment in #2130 rather than making more tickets.