Side navigation
#9255 closed bug (fixed)
Opened May 12, 2011 11:38AM UTC
Closed July 23, 2011 01:27AM UTC
Last modified March 17, 2012 08:54PM UTC
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:
References:
http://www.thespanner.co.uk/2011/03/21/blog-fight-round-two/
Attachments (0)
Change History (6)
Changed May 20, 2011 02:55PM UTC by comment:1
| status: | new → open |
|---|
Changed June 29, 2011 06:52PM UTC by comment:2
| component: | unfiled → ajax |
|---|---|
| priority: | undecided → high |
Changed July 12, 2011 02:51PM UTC by comment:3
This was confirmed during bug triage.
Changed July 23, 2011 01:27AM UTC by comment:4
| resolution: | → fixed |
|---|---|
| status: | open → closed |
Fixes #9255: xml parsing error in $.parseXML is now properly detected for all browsers. Unit test added.
Changeset: 27291ff06ddb655f90a8d1eada71f7ac61499b12
Changed July 23, 2011 01:27AM UTC by comment:5
| milestone: | 1.next → 1.6.3 |
|---|
Changed July 23, 2011 01:27AM UTC by comment:6
| cc: | → jaubourg |
|---|
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.