Select2 - A better way to make select boxes (with jQuery)
41–50 of 60 posts
Re: Select2 - A better way to make select boxes (with jQuery)
#42Re: Select2 - A better way to make select boxes (with jQuery)
#43Re: Select2 - A better way to make select boxes (with jQuery)
#44Re: Select2 - A better way to make select boxes (with jQuery)
#45Re: Select2 - A better way to make select boxes (with jQuery)
#46It breaks normal usage. Tab to a normal Select, press 'n' 3 times and you get New Hampshire (the 3rd item starting with 'n'). Tab to Select2 press 'n' 3 times and you get nothing.
Re: Select2 - A better way to make select boxes (with jQuery)
#47Maybe it's just me, but I tend to dislike loading 50kb (plus the CSS file) scripts into my applications unless the service is built around something that said script adds a ton of value for. I dunno, is 50kb relevant any longer? Still seems like the 50kb to 100kb range matters when adding in js files. At 5kb to 10kb I don't think much about it.
Re: Select2 - A better way to make select boxes (with jQuery)
#48Obligatory: what's the difference between Select2 and Chosen? ( http://news.ycombinator.com/item?id=4074501 )
Re: Select2 - A better way to make select boxes (with jQuery)
#49Is it only me or anybody else finds the multi select annoying and not at all good UX? It looks good but the means to select many values is inefficient and tiresome.
Re: Select2 - A better way to make select boxes (with jQuery)
#50While it's always good to have people exploring improvements to UI elements, it would be superior to have those improvements show up as patches to WebKit or Firefox or GNOME or whatever else. Native UI elements need the improvements; that's where UI actually belongs. On mobile in particular, there's a couple of problems with the web-page approach to UI. One, it adds yet more stuff to download that "shouldn't" be nece…
Good points but I think you're preaching to the choir. The bottleneck is the W3C which is probably bogged with all sorts of red tape and politics.