And yet another control that pretends to be a dropdown box, but isn't. No. I'm not complaining about the appearance or the fact that it has a search field while the real dropdown doesn't. I'm complaining about the way it responds to mouse actions: The real dropdown box, on my machine, expands the menu on mouse down after a no-doubt OS-specific delay. The fake dropdown doesn't - it only reacts on mouse up. Of course,…
Looks fantastic, but here's another feature it doesn't have which makes it feel less native. Try mouse scrolling too far whilst the menu's options are open/visible. The parent page scrolls as well when you reach the start/end. This doesn't happen with a normal select menu. I wonder if there's a way to do an event.preventDefault() on the mouse scroll event when reaching the end of the list?
Chosen: A javascript plug-in that makes long select boxes user-friendly.
21–30 of 81 posts
Re: Chosen: A javascript plug-in that makes long select boxes user-friendly.
#22And yet another control that pretends to be a dropdown box, but isn't. No. I'm not complaining about the appearance or the fact that it has a search field while the real dropdown doesn't. I'm complaining about the way it responds to mouse actions: The real dropdown box, on my machine, expands the menu on mouse down after a no-doubt OS-specific delay. The fake dropdown doesn't - it only reacts on mouse up. Of course,…
My problem with this is that when I see the box (e.g. Multiple Select), I perceive it as a text input. I'd be ill-surprised to discover on a site to (all of a sudden) have this protruding box appear out of nowhere. Better solution: on mouse click, hide the box. Only show the box for autocompletes.
Re: Chosen: A javascript plug-in that makes long select boxes user-friendly.
#23Excellent. Makes you wonder why browser vendors never improved on the usability of such controls themselves.
Re: Chosen: A javascript plug-in that makes long select boxes user-friendly.
#24Re: Chosen: A javascript plug-in that makes long select boxes user-friendly.
#25This nearly completely breaks the select ui on iOS. It should do some kind of feature detection so that it can disable itself on browsers that have alternate ui's for controls like this. For example, this converts a select menu to an input field. On iOS the keyboard comes up instead of the select control.
Re: Chosen: A javascript plug-in that makes long select boxes user-friendly.
#26Does anyone know if it's compatible with formalize.me? Does it work well on android/iphone?
Re: Chosen: A javascript plug-in that makes long select boxes user-friendly.
#27This project looks awesome. This stuff is annoying to have to replicate yourself, and I'm glad to see MooTools support as well. That said, my first reaction when looking at the first Country dropdown example was that I liked the native one better since in OS X it shows me dozens of choices at once (fills most of the screen vertically) and then in the "after" suddenly I was constrained to only seeing 7 countries at a…
Agreed. Also, when a user has to access both your desktop and mobile apps, the experience has to be the same. This plugin, however nice, is trying to solve a problem by further modifying the problematic feature. Just remove the select if your list is too long; there should really only be a handful of options contained within. As a rule, I keep it to five and I never replace the pseudo element with plugins.
Re: Chosen: A javascript plug-in that makes long select boxes user-friendly.
#28This nearly completely breaks the select ui on iOS. It should do some kind of feature detection so that it can disable itself on browsers that have alternate ui's for controls like this. For example, this converts a select menu to an input field. On iOS the keyboard comes up instead of the select control.
Re: Chosen: A javascript plug-in that makes long select boxes user-friendly.
#29Re: Chosen: A javascript plug-in that makes long select boxes user-friendly.
#30This nearly completely breaks the select ui on iOS. It should do some kind of feature detection so that it can disable itself on browsers that have alternate ui's for controls like this. For example, this converts a select menu to an input field. On iOS the keyboard comes up instead of the select control.
This just seems like a matter of preference to me. It works on iOS pretty much just like it works on a desktop. It may be that some iOS users would prefer the native UI, but you could say the same for some desktop users (particularly keyboard-wary ones). I certainly wouldn't call anything "broken".
On the desktop the element still feels like a . On the iPhone it feels nothing at all like a