Side navigation
#12422 closed bug (invalid)
Opened August 29, 2012 10:49AM UTC
Closed August 29, 2012 12:10PM UTC
Last modified August 31, 2012 02:43PM UTC
Opera 12 error - Unhandled DOMException: SYNTAX_ERR
Reported by: | necolas | Owned by: | |
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | 1.8.0 |
Keywords: | Cc: | miketaylr | |
Blocked by: | Blocking: |
Description
Opera 12's dev tools report an "Unhandled DOMException: SYNTAX_ERR" in jQuery 1.8.0. Doesn't happen in 1.7.2.
Previously discussed here and reproduced in Opera 9.8 - http://my.opera.com/community/forums/topic.dml?id=1513672
Cannot reproduce in Firefox or Chrome.
Example: http://demo.html5boilerplate.com/
Attachments (0)
Change History (5)
Changed August 29, 2012 10:53AM UTC by comment:1
status: | new → open |
---|
Changed August 29, 2012 10:54AM UTC by comment:2
Previously discussed here and reproduced in Opera 9.8 - http://my.opera.com/community/forums/topic.dml?id=1513672
Note that they’re actually talking about the latest stable Opera release as well. (There is no Opera 9.8; only the user agent string says that.)
Changed August 29, 2012 12:10PM UTC by comment:3
resolution: | → invalid |
---|---|
status: | open → closed |
Here is a screen shot: http://i.imgur.com/TE6hS.png
These are all just false positives from internal situations where we have exceptions caught. I see this one in jsfiddle.net as well without jQuery: http://i.imgur.com/yrZSb.png
In both cases it is clearly not an **unhandled** exception, the try-catch is RIGHT THERE above the line that throws. The only way I can see to avoid it breaking is to turn off the "Show parse errors and break on exceptions" although I'd prefer to still show parse error and only break on unhandled exceptions.
Changed August 29, 2012 12:17PM UTC by comment:4
cc: | → miketaylr |
---|
Changed August 31, 2012 02:43PM UTC by comment:5
12.50 does not stop on handled exception by default anymore. So yeah.