Skip to main content

Bug Tracker

Side navigation

#14565 closed bug (wontfix)

Opened November 21, 2013 03:48PM UTC

Closed December 09, 2013 02:33PM UTC

slideToggle callback error causes infinite loop

Reported by: anonymous Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 1.10.2
Keywords: Cc:
Blocked by: Blocking:
Description

I have a case where I am calling .each from within the callback of slideToggle. If an error happens

inside that .each, an infinite loop is created and the error repeats forever.

I have an example showing how the problem is isolated to the slideToggle callback. This seems to happen in all versions.

http://jsfiddle.net/wvyNz/15/

Attachments (0)
Change History (4)

Changed December 06, 2013 06:11PM UTC by timmywil comment:1

description: I have a case where I am calling .each from within the callback of slideToggle. If an error happens \ inside that .each, an infinite loop is created and the error repeats forever. \ \ I have an example showing how the problem is isolated to the slideToggle callback. This seems to happen in all versions. \ \ To get around the spam filter, the following is the path to a JS Fiddle: \ \ wvyNz SLASH 15I have a case where I am calling .each from within the callback of slideToggle. If an error happens \ inside that .each, an infinite loop is created and the error repeats forever. \ \ I have an example showing how the problem is isolated to the slideToggle callback. This seems to happen in all versions. \ \ http://jsfiddle.net/wvyNz/15/

Changed December 06, 2013 06:15PM UTC by timmywil comment:2

This seems like another case where we would have to catch the exception, which jQuery avoids for debugging purposes. What are the team's thoughts on the desired behavior here?

Changed December 08, 2013 03:28PM UTC by dmethvin comment:3

It's not a "loop", the animation just fails to progress because of the error. If you open the console and look at the trace, the error message makes it pretty clear where the problem is happening. Swallowing the error would obfuscate things and make it difficult to debug. I'd vote for leaving it as is.

Changed December 09, 2013 02:33PM UTC by timmywil comment:4

resolution: → wontfix
status: newclosed

Agreed.