adding ability to disable a ui-select by setting its ancestor fieldset's disabled property

[ghost]

Disabling the root ui-select element works just fine, however something like this:

<fieldset disabled>
    <ui-select ...>
        ...
    </ui-select>
</fieldset>

does not disable the ui-select control.

my changes to the code make this work.

[AdamAxtmann]

Alternatively, adding a watch on the focusser works without doing DOM traversal.

    attrs.$observe('disabled', function() {
      // No need to use $eval() (thanks to ng-disabled) since we already get a boolean instead of a string
      $select.disabledFlag = attrs.disabled !== undefined ? attrs.disabled : false;
      $select.disabled = $select.disabledFlag || $select.disabledSelector;
    });

    scope.$watch(function () { return focusser.is(":disabled"); }, function (value) {
      $select.disabledSelector = value;
      $select.disabled = $select.disabledFlag || $select.disabledSelector;
    });

Then we just remove ng-disabled from the input element.

    //Don't disable this field, since it's css selector (:disabled) is being monitored to identify if it's in a fieldset.
    var focusser = angular.element("<input class='ui-select-focusser ui-select-offscreen' type='text' aria-haspopup='true' role='button' />");

See my pull request here: #445

[buraktamturk]

Any good reason for not merging this? This is definitely must have feature for a form element. I can control all of my form fields using fieldset except ui-select, in case I need to add same ng-disabled expression to ui-selects. Just why?

[portus84]

+1

[Sheeryada]

+1

[eugeneos]

+1

[AdamAxtmann]

This hasn't been merged because it's failing build tests. See #772 for a working fix.

[wesleycho]

Closing due to being superceded as mentioned in comments & due to age.