On Sep 29, 2012, at 4:51 AM, Daniel Friesen <daniel(a)nadir-seen-fire.com
wrote:
Yes, multiselect is a VERY bad usability choice.
Frankly we shouldn't use
it anywhere. If we're using JS to make
a better UI it would actually be much better to output
usable checkboxes
and then turn the checkboxes into a
special JS multi-select. Instead of outputting an
unusable multi-select
and compensating for it.
Sure, as long as there is JS available we should
turn the multi-select into
something nicer. But the original idea behind this was that a multi select
would still be more user friendly than an endless list of check-boxes when
having around 300 choices (e.g. for languages).
Take jQuery chosen for example (thanks for the link Yury), it takes a
multi-select as source and turns it into some very nice piece of UI. It
doesn't matter whether you originally have a bunch of check-boxes or a
multi-select from a JS perspective.
Anyhow, I would still appreciate if someone would merge the thing, it's
sitting around for too long already and it seems that it got stuck because
of some very minor issue once again:
https://gerrit.wikimedia.org/r/#/c/8924/
Thanks!
--
Daniel Werner
Software Engineer
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.