ngOptions: non-grouped options shouldn't float to the top when using group by

[tdakhla]

Example fiddle where non-grouped options incorrectly always float to the top: http://jsfiddle.net/raxzauyL/ (against 1.3.7)

The expected behavior is that the options should be interspersed between the optgroups, not bunched at the top. I've tried setting the group by value to '', undefined, null, and even removing the key from the obj completely, but none seem to work.

[pkozlowski-opensource]

@tdakhla not sure why you saying that

The expected behavior is that the options should be interspersed between the optgroups

IMO the current behaviour has much more sense - you are telling a select box to group items and this is exactly what it does. The micro-syntax doesn't support mixing regular options and optiongroups and honestly I can't think of a variation of it that would support your use-case.

Now, I guess this issue boils down to making sure <select> can be used without micro-syntax (that is, with options / optiongroups generated by users based on the model value).

[tdakhla]

@pkozlowski-opensource I believe that the expected behavior is the non-grouped items displayed in the dropdown respect array ordering as much as possible, even when using group by. It's definitely possible to have an array with out of order grouped items (http://jsfiddle.net/wv4swhpn/), and the resulting behavior is fine in this case (first occurrence of a grouped item is where all the grouped items will live), but.. the non-grouped items get put at the top. Given current state behavior, that is definitely a discrepancy as I would expect non-grouped items to be bunched where the first non-grouped item lives. However, since I don't believe that non-grouped items are in any way related to each other, they shouldn't be bunched at the top, or even where the first non-grouped item lives - they should remain where they are in the list.

[petebacondarwin]

This is fixed by #10639

See http://jsfiddle.net/su61n9m9/