Skip to main content

Bug Tracker

Side navigation

#13496 closed bug (notabug)

Opened February 21, 2013 06:29PM UTC

Closed February 21, 2013 08:56PM UTC

jQuery unresponsive - incrementing "elems" when attempting to remove child div

Reported by: Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 1.8.2
Keywords: Cc:
Blocked by: Blocking:

I haven't reproduced a minimal case but in my rails dev environment, using jQuery 1.8.2 and twitter bootstrap 2.2.2, the browser, in a certain circumstance, is crashing due to jQuery being unresponsive.

When trying to load an image asset that will 404 inside a div that is hidden by bootstrap, that's when jQuery will become unresponsive. Inspecting with firebug, the debugger never moves past line 6348 -

div.parentNode.removeChild( div );

On each continue, the only difference is "elems" will increment. For example, from "<li><a>177086</a></li>" to "<li><a>177087</a></li>".

Like I explain here, I can load the page when above the width that shows the 404 asset and size down just fine. Loading the page when width < 767px is when jquery becomes unresponsive.

The difference in the rails console is loading below 767px, the last valid assets is served and just stops. Above 767px the 404 assets reports

Started GET "/assets/bg_direction_nav.png" for at 2013-02-21 13:27:03 -0500
Served asset /bg_direction_nav.png - 404 Not Found (30ms)

ActionController::RoutingError (No route matches [GET] "/assets/bg_direction_nav.png"):

Rendered /usr/local/rvm/gems/ruby-1.9.2-p180/gems/actionpack-3.1.10/lib/action_dispatch/middleware/templates/rescues/routing_error.erb within rescues/layout (1.0ms)

This may be a bootstrap bug, a rails bug or a jquery bug. Any information is appreciated.

Attachments (0)
Change History (3)

Changed February 21, 2013 06:59PM UTC by rwaldron comment:1

owner: →
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket!

Additionally, be sure to test against the "jQuery (edge)" version to ensure the issue still exists—you may need to change this to a specific version depending on the test case.

To get you started, use this boilerplate: Open the link and click to "Fork" (in the top menu) to begin.

Also, please read:

Changed February 21, 2013 08:42PM UTC by anonymous comment:2

This can be closed! The issue was a conflict between woothemes flexslider and twitter bootstrap which caused the infinite loop in jQuery.

Changed February 21, 2013 08:56PM UTC by scottgonzalez comment:3

resolution: → notabug
status: pendingclosed