Skip to main content

Bug Tracker

Side navigation

#11478 closed bug (invalid)

Opened March 16, 2012 12:04AM UTC

Closed March 17, 2012 04:33PM UTC

Last modified December 04, 2013 08:38PM UTC

DOMException in Google Chrome

Reported by: Owned by:
Priority: low Milestone: None
Component: misc Version: 1.7.1
Keywords: Cc:
Blocked by: Blocking:

When Developer Tools is open Google Chrome is pausing execution at

Sizzle.matchesSelector, jquery-1.7.1.js:5121

showing a message "Paused on exception: 'DOMException'".

I have tried with some previous versions(1.5.1, 1.5.2, 1.6.1) of jquery, but did the same.

Attachments (0)
Change History (9)

Changed March 16, 2012 12:05AM UTC by comment:1

My Chrome version is 17.0.963.66.

Changed March 17, 2012 07:32AM UTC by comment:2

its ok now :)

it caused by a chrome setting i didn't noticed.

Changed March 17, 2012 04:33PM UTC by sindresorhus comment:3

component: unfiledmisc
priority: undecidedlow
resolution: → invalid
status: newclosed

Changed April 28, 2012 05:33AM UTC by comment:4

Just for the others ran in the same problem. You should switch "Pause on all exceptions" to "Pause on uncaught exceptions" so that the Chrome don't stop at every try-catch block:


Changed July 18, 2012 09:22AM UTC by Ricardo Peres comment:5

The thing is, "Pause on all exceptions" is a very useful thing... I believe jQuery should not throw any kind of exceptions, because if it does, we will be continuously distracted by them and won't know whether they are important - these don't seem so - or not.

Just my 5 cents...

Changed July 18, 2012 12:36PM UTC by dmethvin comment:6

I believe jQuery should not throw any kind of exceptions

Sometimes we do operations that throw exceptions, and it's unavoidable. As long as we catch them it shouldn't be a problem. If you'd like to inspect the places where we do that and recommend another course of action, that would be welcome.

Changed September 11, 2013 09:25PM UTC by dmethvin comment:7

#14350 is a duplicate of this ticket.

Changed November 12, 2013 09:35PM UTC by comment:8

This ends up being very annoying in our development environment as well. All our developers and our QA are trained to use the 'stop on exception' to keep our code clean. In addition our automated tests stop on exceptions.

Changed December 04, 2013 08:38PM UTC by anonymous comment:9

invalid bug?