Addepar
Disable doesn't work for select or multi-select
I've posted a question about this on stackoverflow. I don't really understand why the disabled property doesn't work in the multi-select-component, since it seems to inherit from the select-component where it does work. Cheers.
http://stackoverflow.com/questions/25375319/how-to-disable-multi-select-component-in-ember-widgets
Looks like a bug to me; I've edited your title here and tagged it as a bug. A workaround like the one you posted might be your best bet if you want a quick-fix. If you're able to fix the source of the problem in ember-widgets, we'll definitely get it merged in.
Also thanks for providing a JS Bin in your stack overflow question! For reference: http://jsbin.com/subekubi/5/edit.
In the future, if you tag SO questions with "ember-widgets", I'll be more likely to notice them.
Yeah, sorry about that. I tried tagging it with "ember-widgets," but SO said I needed a reputation of 1500 to make new tags. :confused: I'm not all too familiar with coffeescript, but I might take a stab at it.
@azirbel - So I'm having a little difficulty getting started on this bug. I downloaded and installed ember-widgets, but when I tried editing the select-component in select.hbs, it didn't exhibit the same behavior as my JS bin. Instead, it stops rendering anything that is visible, however, I'm still able to tab over to it because it's in the DOM. Would the code at http://rawgit.com/Addepar/ember-widgets/v0.1.0/dist/js/ember-widgets.js be different from what I've downloaded from the master branch?
Oh, I didn't realize ember-widgets wasn't a tag yet. That's too bad.
I just checked what you said, and sure enough - both on master and at v0.1.0, adding disabled=true to the select widget just makes it disappear completely, and doesn't do anything to multi-select. I don't know why it's different in the JS Bin, but fixing it in the demo app is probably the best way to start. Sounds like it's even more buggy than we thought, sorry about that.