Opened 12 years ago
Closed 12 years ago
#8438 closed bug (fixed)
Bad debugging
Reported by: | Owned by: | jaubourg | |
---|---|---|---|
Priority: | low | Milestone: | 1.5.2 |
Component: | core | Version: | 1.5.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Change History (7)
comment:1 Changed 12 years ago by
Owner: | set to [email protected]… |
---|---|
Status: | new → pending |
comment:2 Changed 12 years ago by
Status: | pending → new |
---|
I can't provide any tests, just sreenshots :(
comment:3 Changed 12 years ago by
Status: | new → pending |
---|
Does this same issue occur when you use the non-minified version?
comment:4 Changed 12 years ago by
Component: | unfiled → core |
---|
comment:5 Changed 12 years ago by
Status: | pending → new |
---|
Yes,
1.5.1.min.js vs 1.5.1.js http://dl.dropbox.com/u/1022216/bugs/jq1.5.1.min.png http://dl.dropbox.com/u/1022216/bugs/jq1.5.1.nom.png
You can reproduce this in Google Chrome by making throw error (access to undeclared var, etc.) in success event of $.ajax (I think it's reproduceable in any events binded with jquery)
comment:6 Changed 12 years ago by
Milestone: | 1.next → 1.5.2 |
---|---|
Owner: | changed from [email protected]… to jaubourg |
Priority: | undecided → low |
Status: | new → assigned |
comment:7 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Thanks for taking the time to contribute to the jQuery project! Please provide a reduced jsFiddle test case to help us assess your ticket!
Additionally, test against the jQuery 0 GIT version to ensure the issue still exists.