Skip to main content

Bug Tracker

Side navigation

#2942 closed bug (invalid)

Opened May 27, 2008 03:20PM UTC

Closed May 27, 2008 10:08PM UTC

Last modified March 14, 2012 10:17PM UTC

"Too much recursion" error thrown by blockUI

Reported by: Heliologue Owned by:
Priority: major Milestone: 1.3
Component: core Version: 1.2.5
Keywords: Cc:
Blocked by: Blocking:
Description

Since updating to jQuery 1.2.6, the function to close a blockUI (2.07) invocation causes Firefox (+Firebug) to throw a "Too recursion" error and the CPU to spike--the UI is never unblocked.

IE is unaffected. jQuery 1.2.3 throws no such errors.

For the sake of context, here's our implementation:

$(document).ready(function() {
                $.blockUI({ 
                message: 'You have unread messages.<br /><a href="/usfportal/secure/general/myBannerMessages.jsp">Click here to read them</a><br /><br /><button type="button" class="jqmClose" value="Close This Notification">Close this notification</button>',
                    css: {
                        backgroundImage: 'url(/images/alert.png)',
                        backgroundPosition: 'center top', 
                        backgroundColor: '#FFF6BF',
                        border: '2px solid #FFD324', 
                        backgroundRepeat: 'no-repeat',
                        padding:'35px 20px 20px 20px',
                        fontSize: '1.2em',
                        top: '30%',
                        fontWeight: 'bold'
                        }
                }); 
                $('.jqmClose').click($.unblockUI); // if they click close, unblock the UI
            });
Attachments (0)
Change History (3)

Changed May 27, 2008 03:36PM UTC by Heliologue comment:1

A very simple test case is available at http://heliologue.com/host/test_case

Changed May 27, 2008 06:59PM UTC by Heliologue comment:2

On advice from Mike Alsup, writing the close function out properly fixes the issue

.click($.unblockUI) --> click(function() { $.unblockUI(); });

I don't remember why I shortcut it before, but the new jQuery release seems to have put a stop to it.

This should be closed as a non-issue.

Changed May 27, 2008 10:08PM UTC by flesler comment:3

milestone: → 1.3
resolution: → invalid
status: newclosed