IE long running script crashes [#1308766]

Adding a small number of moderatlely sized taxonomies to a content type cause IE7 and IE8(not tested others) to crash (or hang). Usually throwing a long running script error. Particular example is if the trees are selected to load collapased, the recursive code that iterates over tree to find already selected nodes overloads the IE Javascript engine.

Comments

Comment #1

Anonymous (not verified) commented 20 January 2012 at 22:35

I am having the same issue, I get script errors when trying to create a node in IE. The tree is not collapsed as it should be.

Comment #2

bartk commented 22 March 2012 at 21:25

Status:

Active

» Closed (fixed)

Fixed in 7.x-1.x-dev. Figuring out which parts of the tree are initially closed is now done on the server side.

Comment #3

larskleiner commented 30 May 2012 at 09:54

Status:

Closed (fixed)

» Active

I just installed 7.x-1.x-dev and get a long running script error in IE8. When I terminate the script I end up getting only one or two levels of a four level hierarchy selected in an uncollapsed tree.

Comment #4

odegard commented 11 June 2012 at 08:50

Seems there's an issue with find() and IE8:

http://ethermuse.blogspot.no/2011/07/jquery-find-slow-in-ie8.html

In the same article there's a suggestion for how to use children(), filter() and attributes() to circumvent find().

I guess one way to solve this for multilevel lists is to make a recursive function to find all checkboxes. Sadly, this is beyond my abilities so I can't do much more myself. I'd like to test though if someone feel they want to take on the challenge.

Comment #5

geerlingguy commented 14 June 2013 at 18:40

Version:

7.x-1.6

» 7.x-1.x-dev

I've been getting errors as well, with IE8. If I comment out the $('.term-reference-tree', context).each(function() { function completely, I don't have any trouble anymore. What is that code for? It speaks of track lists and maximum selections and such, but I don't see any configuration for that in the interface...

I don't see why we'd want to do all of that unless that setting is already active (or the setting to check all items below the parent level checkbox). Any time I check or uncheck an item in the top levels of the vocabulary (with sometimes 100-200 children), the page takes 2-4 seconds to respond in Chrome, and basically freezes IE. If I comment out the .each() function, everything works the same, but it works instantly.