Page MenuHomePhabricator

Selects in Special:AggregateGroups too messy if a lot of pages are marked for translation
Closed, ResolvedPublic


Screenshot of [[:m:Special:AggregateGroups]] showing an open HTML select element

At meta, there are currently about 350 pages marked for translation. When it comes to aggregating them to groups, the huge select element is simply unhandy. A JSON-service would be the ideal solution, IMHO.

Version: unspecified
Severity: normal
See Also:


without_chosen.png (867×1 px, 43 KB)



Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:00 AM
bzimport set Reference to bz52216.
bzimport added a subscriber: Unknown Object (MLST).

Created attachment 13003
This is how it will look like after using jquery.chosen.

After switching chosen to select2 (Bug 51443) it will be possible to even use JSON services without having to change the UI again.

Note that there will be the point when you *have to* offer a JSON service or the page will simply crash. This is issue by design.


chosen_use.png (506×553 px, 19 KB)

Change 76503 had a related patch set uploaded by Rillke:
Make Special:AggregateGroups using jquery.chosen

Change 76503 merged by jenkins-bot:
Make Special:AggregateGroups using jquery.chosen

Rillke, do you consider this solved?

(In reply to comment #4)
Yes, this very specific request. But not the issue itself.