fix(ngOptions): don't change user selections while <select> open in fire...

[heymatthew]

Sample patch that fixes issue #6679 but may regress parts of the code base.

I'm finding it difficult to verify the test suite because these unit tests are failing for me in New Zealand (see issue #5017). But time zone errors aside, I believe my patch breaks subtly with this output:

Chrome 33.0.1750 (Linux) select ngOptions binding should select correct input if previously selected option was "?" FAILED
  Expected '1' to equal '0'.
  Error: Expected '1' to equal '0'.
      at null.<anonymous> (/home/mbgray/workspace/angular.js/test/ng/directive/selectSpec.js:965:31)
  Expected false to be truthy.
  Error: Expected false to be truthy.
      at null.<anonymous> (/home/mbgray/workspace/angular.js/test/ng/directive/selectSpec.js:966:63)

I'm submitting it anyway because it might be a starting point for conversation and other fixes. I'm not as comfortable this deep in the framework and didn't know how to take this further.

[mary-poppins]

Thanks for the PR! Please check the items below to help us merge this faster. See the contributing docs for more information.

• Uses the issue template (#6680)

If you need to make changes to your pull request, you can update the commit with git commit --amend.
Then, update the pull request with git push -f.

Thanks again for your help!

[Narretz]

I think this is a fix for the same thing: #5994 (but without the regression)

[heymatthew]

@Narretz yep, looks like the same issue. I didn't see that one, cheers for pointing it out. I'll close #6680 in favor of #5994.

[IgorMinar]

since this is a dupe, I'm closing it. thanks!