Bug. Select ng-options with multiple doesn't work IE10/11 when next to each other.

[wawyed]

There seems to be an issue in IE10/11 using select with multiple attribute. The issue only seems to be happening when you have more than one select in a page. The unexpected behaviour renders all of the selects unresponsive minus the last one. It would appear to be a rendering issue, since if you toggle the visibility of the element it works as intended.

Here is a plnkr to reproduce the issue: http://plnkr.co/edit/E1asWesEj90OqAf5RIt2?p=preview

[Narretz]

That was difficult to debug ...
Turns out IE(11) has a problem with this line where the label property is assigned:https://github.com/angular/angular.js/blob/v1.4.0-beta.6/src/ng/directive/ngOptions.js#L513

Previously, the whole template cloning / assigning was wrapped in jqlite. I guess we cannot simply skip the label assignment - theoretically it should be set to the text always, but I don't know if that works in all browsers.

The problem is that currently the bug appears regardless of which way the label is set: vanilla, $.prop, $.attr

[Narretz]

This is a crazy bug. It only happens if the first select is wrapped in an element with display: blockor display: inline-block (possibly others).
It's also not possible to test this in a unit test with browserTrigger. I assume because the select is completely blocked to any user interaction, but browserTrigger dispatches the event directly from the DOM.