This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Multiple select boxes (size > 1) freezes under asynchronous conditions in IE11 #13239
Milestone
Comments
|
Oh, it's this bug again. This is seriously one of the most ridiculous bugs I've ever seen. I assume I can count myself lucky that I never had to support IE6-7. |
|
http://plnkr.co/edit/UZGWX9?p=preview |
|
@rockyrfernandes are there any specific steps to produce the bug i your plunker? I'm just clicking around and can't seem to get the selectbox to freeze, neither in chrome nor in IE11. |
|
same issue. n in angular v1.3 17. |
Narretz
added a commit
to Narretz/angular.js
that referenced
this issue
Apr 11, 2016
This changes the way option elements are generated when the ngOption collection changes. Previously, we would re-use option elements when possible (updating their text and label). Now, we first remove all currently displayed options and the create new options for the collection. The new options are first appended to a documentFragment, which is in the end appended to the selectElement. Using documentFragment improves render performance in IE with large option collections (> 100 elements) considerably. Always creating new options fixes issues in IE where the select would become unresponsive to user input. Fixes angular#13607 Fixes angular#13239 Fixes angular#12076
Narretz
added a commit
to Narretz/angular.js
that referenced
this issue
Apr 12, 2016
This changes the way option elements are generated when the ngOption collection changes. Previously, we would re-use option elements when possible (updating their text and label). Now, we first remove all currently displayed options and the create new options for the collection. The new options are first appended to a documentFragment, which is in the end appended to the selectElement. Using documentFragment improves render performance in IE with large option collections (> 100 elements) considerably. Creating new options from scratch fixes issues in IE where the select would become unresponsive to user input. Fixes angular#13607 Fixes angular#13239 Fixes angular#12076
Narretz
added a commit
that referenced
this issue
Apr 13, 2016
This changes the way option elements are generated when the ngOption collection changes. Previously, we would re-use option elements when possible (updating their text and label). Now, we first remove all currently displayed options and the create new options for the collection. The new options are first appended to a documentFragment, which is in the end appended to the selectElement. Using documentFragment improves render performance in IE with large option collections (> 100 elements) considerably. Creating new options from scratch fixes issues in IE where the select would become unresponsive to user input. Fixes #13607 Fixes #13239 Fixes #12076
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We're having issues with select boxes, where selection in one box leads to an asynchronus load of options for the next select box. In IE11 the select boxes will freeze until somthing as simple as setting visibility to hidden and back again.
I have reproduced this in this plunker: http://plnkr.co/edit/NGwG1LUVk3ctGOsX15KI?p=preview
If you fiddle around with the topmost select, the second and third select will often freeze. One interesting thing is that if you open the plunker in its own window, the freezing will not happen. I have tested this with 1.4.7 and 1.5.0-beta-1.
This seems like similar problem to #11314 and #11795 one thing being different is the async behaviour.
The text was updated successfully, but these errors were encountered: