Skip to main content

Bug Tracker

Side navigation

#14008 closed bug (notabug)

Opened June 11, 2013 03:07PM UTC

Closed June 12, 2013 06:09PM UTC

Last modified June 13, 2013 08:55PM UTC

exceptions inside jquery

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

I've recently upgraded to jQuery 2.0.2 from jQuery 1.8.3.

While before it was possible to use "Pause on all exceptions" in webdeveloper from google chrome, there are now so many exceptions inside the jquery source it's not usable anymore.

Happens in both versions, debug and minimized.

Attachments (0)
Change History (6)

Changed June 11, 2013 04:32PM UTC by dmethvin comment:1

owner: →
status: newpending

Can you post an example on jsfiddle that demonstrates the problem?

Changed June 12, 2013 04:02PM UTC by comment:2

status: pendingnew

even the simplest thing produces an exception in current google chrome webdeveloper.

i.e. see

clicking "run" first catches in jquery-2.0.2.js line 1571, and after continue in the debugger again in line 1588.

Changed June 12, 2013 06:09PM UTC by timmywil comment:3

resolution: → notabug
status: newclosed

I only see 2 when breaking on all exceptions. However, even if there were more, they are expected.

By the way, I only see 2 exceptions when excluding jsfiddle scripts by going to the /show url.

Changed June 12, 2013 09:00PM UTC by dmethvin comment:4

And to be clear, jQuery needs to be able to trap exceptions with try/catch. We don't like doing it for this very reason, but sometimes there are no other reasonable options.

Changed June 13, 2013 02:06PM UTC by comment:5

exceptions for diagnosis and setup sounds fine, but exceptions at runtime?

I've done some more fiddling and narrowed down my real problem to exceptions in xml processing:

looking at and clicking on the yellow div, each click now results in a catch in jquery-2.0.2.js line 1394 and then some more ...

do I need to open a new report for this?

Changed June 13, 2013 08:55PM UTC by timmywil comment:6 Those are also feature tests. Sizzle re-runs support tests (and caches the results) related to documents whenever the context is changed to something new. When parsing XML, the context changed to an XML document so it re-ran the tests (and failed a few more since it's XML) and then ran them again when the context when back to an HTML document.