select: multiple attribute only checks for existence but docs indicate that it evaluates true/false

[myagoo]

If I want to tell wether a md-select should be multiple from a scope key, I must do this :

<md-select ng-if="multiple" multiple .../>
<md-select ng-if="!multiple" .../>

Because all those lines have the same behavior, they set initialize the select as multiple :

<md-select multiple="true" .../>
<md-select multiple="false" .../>
<md-select multiple="{{true}}" .../>
<md-select multiple="{{false}}" .../>

In the source code of md-select directive, I can see this LoC :
https://github.com/angular/material/blob/master/src/components/select/select.js#L387
I can understand why all 4 lines have the same behavior.

So I tried to use ng-multiple and the select started to work correctly... in appearance only : the model is now all messed up.

Here is a codepen where you can see select behavior and the associated model : http://codepen.io/myagoo/pen/OVWGqz

[dharitdesai]

+1

[pdore-netfore]

+1

[nextsoftpl]

+1

[danicomas]

No news?

[Splaktar]

Re-opening this one as the CodePen is still valid and this issue still exists.

[Splaktar]

This seems to be partially related to angular/angular.js@d87fa00 where binding to multiple on select elements was disabled in AngularJS 1.2.0.

[Splaktar]

There is a lot more discussion related to that in:
angular/angular.js#3230
angular/angular.js#3337

[Splaktar]

As mentioned in those issues and #9705, ng-multiple was also removed in AngularJS 1.2.0.

We need to remove it from AngularJS Material as well. This removal is being tracked in #9705.

[Splaktar]

The docs are going to be updated to state:

multiple boolean When present, allows for more than one option to be selected. The model is an array with the selected choices. Note: This attribute is only evaluated once; it is not watched.

Any value that is passed into the multiple attribute will be ignored.