Ticket #11478 (closed bug: invalid)
DOMException in Google Chrome
| Reported by: | sarowar.cse@… | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | None |
| Component: | misc | Version: | 1.7.1 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
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.
Change History
comment:2 Changed 14 months ago by sarowar.cse@…
its ok now :)
it caused by a chrome setting i didn't noticed.
comment:3 Changed 14 months ago by sindresorhus
- Priority changed from undecided to low
- Resolution set to invalid
- Status changed from new to closed
- Component changed from unfiled to misc
comment:4 Changed 13 months ago by stan@…
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:
comment:5 Changed 10 months ago by Ricardo Peres
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...
comment:6 Changed 10 months ago by dmethvin
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.
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
My Chrome version is 17.0.963.66.