W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

RE: DOMParser Errors Should Be Exceptions

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Fri, 13 Jul 2012 22:29:27 +0000
To: Yehuda Katz <yehuda.katz@jquery.com>, Tony Ross <tross@microsoft.com>
CC: Joćo Eiras <joaoe@opera.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <9768D477C67135458BF978A45BCF9B38383D483F@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
Note, I filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=17775
to make this change.

From: wycats@gmail.com [mailto:wycats@gmail.com] On Behalf Of Yehuda Katz
Sent: Wednesday, July 11, 2012 9:12 PM
To: Tony Ross
Cc: Joćo Eiras; public-webapps@w3.org
Subject: Re: DOMParser Errors Should Be Exceptions

If this is the case, can we consider changing the spec?

Yehuda Katz
(ph) 718.877.1325

On Wed, May 23, 2012 at 12:38 PM, Tony Ross <tross@microsoft.com<mailto:tross@microsoft.com>> wrote:
> From: Joćo Eiras [mailto:joaoe@opera.com<mailto:joaoe@opera.com>]

> Opera thrown an exception long time ago and since version 9.5 it changed
> the behavior to return the bogus parsererror tree because it caused
> yahoo mail to fail back them (among other things).
>
> While the current behavior of returning the parsererror document is
> inappropriate, I afraid it also unchangeable.
Has this been examined recently? In IE9+ DOMParser throws an exception when an XML parsing error is encountered. I've yet to hear of this causing a problem.

-Tony
Received on Friday, 13 July 2012 22:30:03 GMT

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