#11478 closed bug (invalid)
DOMException in Google Chrome
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | low | Milestone: | None |
| Component: | misc | Version: | 1.7.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
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 (9)
comment:1 Changed 5 years ago by
comment:3 Changed 5 years ago by
| Component: | unfiled → misc |
|---|---|
| Priority: | undecided → low |
| Resolution: | → invalid |
| Status: | new → closed |
comment:4 Changed 5 years ago by
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 5 years ago by
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 5 years ago by
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.
comment:8 Changed 4 years ago by
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.
My Chrome version is 17.0.963.66.