: Re: responseXML/responseText exceptions and parseError
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
TED]
> Subject: Re: responseXML/responseText exceptions and parseError
>
> 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
>
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.
And gi
> -Original Message-
> From: Jonas Sicking [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 19, 2008 1:24 AM
> To: Zhenbin Xu
> Cc: Anne van Kesteren; Sunava Dutta; IE8 Core AJAX SWAT Team; public-
> [EMAIL PROTECTED]
> Subject: Re: responseXML/responseText exce
ponseXML/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
> >
Julian Reschke wrote:
Could you please provide some more information or give an example about
when this would be the case?
Here's a simple past example, if I understand your question correctly.
One can set an onerror handler on Window that will trigger if an exception is
thrown and not caugh
Julian Reschke wrote:
Could you please provide some more information or give an example about
when this would be the case?
Here's a simple past example, if I understand your question correctly.
One can set an onerror handler on Window that will trigger if an exception is
thrown and not caugh
Julian Reschke wrote:
timeless wrote:
On Thu, Jun 19, 2008 at 1:09 PM, Julian Reschke
<[EMAIL PROTECTED]> wrote:
Can you provide an example where providing *XML* parse error information
within *XHR* would be problematic?
i really shouldn't have to. imagine a document that is not CSS and is
timeless wrote:
On Thu, Jun 19, 2008 at 1:09 PM, Julian Reschke <[EMAIL PROTECTED]> wrote:
Can you provide an example where providing *XML* parse error information
within *XHR* would be problematic?
i really shouldn't have to. imagine a document that is not CSS and is not XML.
now imagine an
On Thu, Jun 19, 2008 at 1:09 PM, Julian Reschke <[EMAIL PROTECTED]> wrote:
> Can you provide an example where providing *XML* parse error information
> within *XHR* would be problematic?
i really shouldn't have to. imagine a document that is not CSS and is not XML.
now imagine an api that lets y
timeless wrote:
generally what i've seen is that exposing some information about a
parse error to a script is a great way to enable data leaks to a
malicious application.
On Thu, Jun 19, 2008 at 11:19 AM, Julian Reschke <[EMAIL PROTECTED]> wrote:
Could you please provide some more information
> generally what i've seen is that exposing some information about a
> parse error to a script is a great way to enable data leaks to a
> malicious application.
On Thu, Jun 19, 2008 at 11:19 AM, Julian Reschke <[EMAIL PROTECTED]> wrote:
> Could you please provide some more information or give an
Zhenbin Xu wrote:
Inline...
-Original Message-
From: Jonas Sicking [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 3:37 PM
To: Anne van Kesteren
Cc: Zhenbin Xu; Sunava Dutta; IE8 Core AJAX SWAT Team; public-
[EMAIL PROTECTED]
Subject: Re: responseXML/responseText exceptions and
timeless wrote:
Ian Hickson wrote:
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.)
On 6/19/08, Julian Reschke <[EMAIL PROTECTED]> wrote:
That's useful,
Ian Hickson wrote:
> 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.)
On 6/19/08, Julian Reschke <[EMAIL PROTECTED]> wrote:
> That's useful, but IMHO not
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 incor
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 con
Inline...
> -Original Message-
> From: Jonas Sicking [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2008 3:37 PM
> To: Anne van Kesteren
> Cc: Zhenbin Xu; Sunava Dutta; IE8 Core AJAX SWAT Team; public-
> [EMAIL PROTECTED]
> Subject: Re: responseXML/respon
Anne van Kesteren wrote:
On Tue, 17 Jun 2008 10:29:12 +0200, Zhenbin Xu
<[EMAIL PROTECTED]> wrote:
Technically because all other XHR methods/properties throw exceptions
in case of state violation, exception for responseXML/responseText is
better.
The reason these don't throw an exception a
On Tue, 17 Jun 2008 10:29:12 +0200, Zhenbin Xu <[EMAIL PROTECTED]>
wrote:
Technically because all other XHR methods/properties throw exceptions
in case of state violation, exception for responseXML/responseText is
better.
The reason these don't throw an exception anymore is actually docume
20 matches
Mail list logo
