option attribute disabled="disabled"

[lordxor]

I would be great if Select2 will respect attribute disabled="disabled" for option tag.

[ivaynberg]

see #171 for how to access the option and provide a custom formatter that can deal with these options in a way you want. i dont see a good solution out of the box because half the users will want to render them as disabled and the other will want to hide them. provide your own custom formatter to deal with it as you like.

[loxK]

I think this issue should be reopened. The "disabled" parameter of the "option" tag is referenced (http://www.w3schools.com/tags/att_option_disabled.asp)

By default Select2 should act like on a regular select box does: grayed out and unselectable.

Up to anyone to hack it using a custom formatter if it wants a non standard behavior.

[mallim]

I agreed with what loxK had said.

By default, Select2 should respect option tag's disabled="disabled"

[bushizhang]

^ I also agree with the above. I've been looking around for nice ways to disable options in Select2.

[aberios]

This is definitely a case where select2 should probably follow the w3c spec. http://www.w3.org/TR/html401/interact/forms.html#h-17.12.1

[NicholasFisher]

I too agree with the agreement that "Select2 should respect option tag's disabled="disabled""

[blakemcintyre]

I would also like to see this.

[joeybagofdonuts]

I'm running into the same problem. Allowing an option's tag to be disabled would solve my problem

[shyndman]

It would be nice to have select2 at feature parity with the standard selects. What do you guys think?

[kevin-brown]

I'm thinking that a pull request works more than a comment. 5 months ago doesn't necessarily reflect the feelings of today.

So, who wants to do it?

[shyndman]

Something about @Ceddy's tone made me think he might want to.

[bushizhang]

Will get around to it after my exams, give me a week or two.

[designosis]

+1 ... disabled="disabled" has been web standard since day 1, not having this implemented is a dealbreaker.