md select null value

[garaboncias]

md-select show selected state even null value is selected (md-input-has-value class is not removed from md-input-container)
demo:
http://codepen.io/anon/pen/vLRjZo

workaround: if first md-options has invalid ng-value (ex: xxxnull) then work as expected (but only if the second md-options use value instead of ng-value which is not documented but used in demos)

so there are more problems:

1. null value selection not work as expected
2. value attribute is not documented but used in demos
3. demos' codePens on page https://material.angularjs.org/1.0.3/demo/select use localhost:8080 as source for angular material lib not a CDN

[trimox]

This issue also occurs if setting the state to just an empty string value.
ie: <md-option></md-option>

[devversion]

Duplicate of #6504.

[garaboncias]

'menu' spec does't say anything about empty value. Before material v1.0 its works as expected, it has the same behaviour as an input fields because it's looks like the same.
It's a bug (or at least very inconsistent behaviour) that you can't reach the initial state: the label is down when you don't give a value at the beginning, and once you select anything the label float up and stick there.
#6504 is a workaround not a solution.

[topherfangio]

@garaboncias Rather than using null, you can use undefined: http://codepen.io/topherfangio/pen/zBZEeM

This works even in 1.0.3, although there were some styling issues that have been fixed in 1.1.0-RC5.

Does this meet your needs?

[garaboncias]

unfortunately its a semi-working dirty workaround.

1. not working if you not set the model value to null. In the example:
   this.state = null;
2. not working if you use ng-value on md-option (ex. your options are object not a string). In the example:
   <md-option ng-repeat="state in ctrl.states" ng-value="state.abbrev">

[topherfangio]

@garaboncias I see what you mean. Let me dive into it and take a deeper look.