How to use ng-class in select with ng-options

You could create a directive that processed the options after the ngOptions directive is processed that updated them with the appropriate classes.

Update: The old code had a few bugs, and I've learned a bit since I answered this question. Here is a Plunk that was redone in 1.2.2 (but should work in 1.0.X as well)

Here is updated (Nov 30 '13 at 3:17) the Code:

app.directive('optionsClass', function ($parse) {  return {    require: 'select',    link: function(scope, elem, attrs, ngSelect) {      // get the source for the items array that populates the select.      var optionsSourceStr = attrs.ngOptions.split(' ').pop(),      // use $parse to get a function from the options-class attribute      // that you can use to evaluate later.          getOptionsClass = $parse(attrs.optionsClass);      scope.$watch(optionsSourceStr, function(items) {        // when the options source changes loop through its items.        angular.forEach(items, function(item, index) {          // evaluate against the item to get a mapping object for          // for your classes.          var classes = getOptionsClass(item),          // also get the option you're going to need. This can be found          // by looking for the option with the appropriate index in the          // value attribute.              option = elem.find('option[value=' + index + ']');          // now loop through the key/value pairs in the mapping object          // and apply the classes that evaluated to be truthy.          angular.forEach(classes, function(add, className) {            if(add) {              angular.element(option).addClass(className);            }          });        });      });    }  };});

Here's how you'd use it in your markup:

<select ng-model="foo" ng-options="x.name for x in items"         options-class="{ 'is-eligible' : eligible, 'not-eligible': !eligible }"></select>

It works like ng-class does, with the exception that it's on a per-item-in-the-collection basis.

In this scenario you can only apply ng-class only if you use ng-repeat with option tags:

<select ng-model="Blah">  <option ng-repeat="person in persons" ng-class="{red: person.Eligible}">    {{person.Name}}  </option>  </select>

This will give custom class to your 'Eligible' persons, but CSS won't work consistently across bowsers.

Plunker.

I wanted to comment on the accepted answer, but because I don't have enough reputation points, I must add an answer.I know that this is an old question, but comments where recently added to the accepted answer.

For angularjs 1.4.x the proposed directive must be adapted to get it working again.Because of the breaking change in ngOptions, the value of the option isn't anymore the index, so the line

option = elem.find('option[value=' + index + ']');

won't work anymore.

If you change the code in the plunker to

<select ng-model="foo" ng-options="x.id as x.name for x in items"         options-class="{ 'is-eligible' : eligible, 'not-eligible': !eligible }"></select>

As result the value of the option tag will now be

value="number:x" (x is the id of the item object)

Change the directive to

option = elem.find('option[value=\'number:' + item.id + '\']');

to get it working again.

Of course this isn't a generic solution, because what if you have not an id in your object?Then you will find value="object:y" in your option tag where y is a number generated by angularjs, but with this y you can't map to your items.

Hopes this helps some people to get their code again working after the update of angularjs to 1.4.x

I tried also to use the track by in ng-options, but didn't get it to work.Maybe people with more experience in angularjs then me (= my first project in angularjs)?