#9255 closed bug (fixed)
jQuery.parseXML error handling does not work in webkit browsers
| Reported by: | Jan Harmsen | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | 1.6.3 |
| Component: | ajax | Version: | 1.6 |
| Keywords: | Cc: | jaubourg | |
| Blocked by: | Blocking: |
Description
When using jQuery.parseXML() to parse an invalid (not well-formed) XML string, jQuery does not throw an error in Webkit-based browsers. Thus jQuery.parseXML error handling is not reliable.
tested on Chrome 11 and Safari 5.0.5 on OS X 10.6.7
Testcase: http://jsfiddle.net/shfHD/
References: http://www.thespanner.co.uk/2011/03/21/blog-fight-round-two/ https://bugs.webkit.org/show_bug.cgi?id=13057
Change History (6)
comment:1 Changed 12 years ago by
| Status: | new → open |
|---|
comment:2 Changed 12 years ago by
| Component: | unfiled → ajax |
|---|---|
| Priority: | undecided → high |
comment:4 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | open → closed |
Fixes #9255: xml parsing error in $.parseXML is now properly detected for all browsers. Unit test added.
Changeset: 27291ff06ddb655f90a8d1eada71f7ac61499b12
comment:5 Changed 12 years ago by
| Milestone: | 1.next → 1.6.3 |
|---|
comment:6 Changed 12 years ago by
| Cc: | jaubourg added |
|---|
Note: See
TracTickets for help on using
tickets.
Yep, it looks like some browsers throw an error and some return an error document that has to be parsed to check for success. DOMParser.parseFromString isn't part of the standard but it seems like jQuery should provide consistent behavior -- either throw an error or return an error document.