Bug Tracker

Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#14008 closed bug (notabug)

exceptions inside jquery

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

Description

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.

Change History (6)

comment:1 Changed 7 years ago by dmethvin

Owner: set to ray007@…
Status: newpending

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

comment:2 Changed 7 years ago by ray007@…

Status: pendingnew

even the simplest thing produces an exception in current google chrome webdeveloper. i.e. see http://jsfiddle.net/xncsV/ clicking "run" first catches in jquery-2.0.2.js line 1571, and after continue in the debugger again in line 1588.

comment:3 Changed 7 years ago by timmywil

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. http://jsfiddle.net/xncsV/show

comment:4 Changed 7 years ago by dmethvin

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.

comment:5 Changed 7 years ago by ray007@…

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 http://jsfiddle.net/xncsV/1/ 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?

comment:6 Changed 7 years ago by timmywil

@ray007@…: 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.

Note: See TracTickets for help on using tickets.