bug in "properly handle empty & unknown options without ngOptions" commit

[Daniel Nelson]

This commit – https://github.com/angular/angular.js/commit/904b69c745ea4afc1d6ecd2a5f3138c6f947b157,
part of v1.0.0rc6 – says that it will 'reuse an existing empty option
(option with valueset to "") when model is undefined'. However, as the
examples show, this is not the case:

v1.0.0rc5: http://jsfiddle.net/bluejade/NSZ2F/5/
v1.0.0rc6: http://jsfiddle.net/bluejade/NSZ2F/6/
v1.0.1: http://jsfiddle.net/bluejade/NSZ2F/7/

Note that in rc5, it correctly shows the initial "null" state as
"snoopy.lvh.me", but the rc6 and 1.0.1 both add a blank entry and show
that as selected.

Thank You,

Daniel

[Daniel Nelson]

Hello Angular Team, any word on this? Should I open an issue on Github?

Thank You,

Daniel

[Daniel Nelson]

I just discovered that although I'd saved the previous fiddles, they
weren't saved into my account, and the /bluejade/ part of those URLs
made them 404. I'm sending my original email now with correct links:

This commit – https://github.com/angular/angular.js/commit/904b69c745ea4afc1d6ecd2a5f3138c6f947b157,
part of v1.0.0rc6 – says that it will 'reuse an existing empty option
(option with valueset to "") when model is undefined'. However, as the
examples show, this is not the case:

v1.0.0rc5: http://jsfiddle.net/bluejade/72gc3/
v1.0.0rc6: http://jsfiddle.net/bluejade/t9CYb/
v1.0.1: http://jsfiddle.net/bluejade/nP3tc/