W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2008

RE: responseXML/responseText exceptions and parseError

From: Zhenbin Xu <Zhenbin.Xu@microsoft.com>
Date: Thu, 19 Jun 2008 13:47:55 -0700
To: Julian Reschke <julian.reschke@gmx.de>, Ian Hickson <ian@hixie.ch>
CC: Jonas Sicking <jonas@sicking.cc>, Anne van Kesteren <annevk@opera.com>, Sunava Dutta <sunavad@windows.microsoft.com>, IE8 Core AJAX SWAT Team <ieajax@microsoft.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <72F767ADE7C63540BE69CD2722A41F440E9C93E0F2@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>

> -----Original Message-----
> From: Julian Reschke [mailto:julian.reschke@gmx.de]
> Sent: Thursday, June 19, 2008 12:13 AM
> To: Ian Hickson
> Cc: Zhenbin Xu; Jonas Sicking; Anne van Kesteren; Sunava Dutta; IE8
> Core AJAX SWAT Team; public-webapps@w3.org
> Subject: Re: responseXML/responseText exceptions and parseError
>
> Ian Hickson wrote:
> > On Wed, 18 Jun 2008, Zhenbin Xu wrote:
> >> [Zhenbin Xu] Regardless what different browser does today, rich
> parsing
> >> error is an important feature for developers. I have found it can
> >> pinpoint the exact problem that otherwise would have been difficult
> to
> >> identify when I sent incorrectly constructed XML file.
> >
> > Mozilla shows the XML error in its error console, which seem more
> useful
> > than exposing the error to script, really. (I expect other browsers
> do the
> > same but I haven't checked as recently.)
>
> That's useful, but IMHO not nearly as useful as giving the script code
> the ability to access the information. Sometimes errors happens in the
> absence of the developer, and it's useful to have an easy and
> automatable way to get the diagnostics.
>
> BR, Julian
>

[Zhenbin Xu] Agree :-)  One less dependency.
Received on Thursday, 19 June 2008 20:48:25 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:26 GMT