W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [File API] Issue 182 about OperationNotAllowed

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 3 Oct 2011 17:40:29 -0700
Message-ID: <CA+c2ei90-bjtZQiDC18rQdWw=sq=1JubvVZ8pUWNoW5G9_guGg@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: Arun Ranganathan <arun@mozilla.com>, Anne van Kesteren <annevk@opera.com>, public-webapps <public-webapps@w3.org>
On Mon, Oct 3, 2011 at 4:26 PM, Ian Hickson <ian@hixie.ch> wrote:
> On Mon, 3 Oct 2011, Arun Ranganathan wrote:
>> Cc'ing Hixie as well to comment on what HTML might need.
> As far as I'm concerned, what HTML has now is fine (DOMException based
> on how DOM Core defines it).
>> > I'll leave this one for Anne. I personally don't care where the new
>> > strings are defined. Anne seemed to prefer to do it in the DOM4 (aka
>> > DOM Core) spec, but I don't think we want to block on that happening.
>> I don't think we should block on DOM4 either.
> Isn't it already done? It's what HTML is using...

I looked at how for example WebSockets and EventSource exposes error
information. I would have thought in both cases that it would have
been done as a property on the websocket/eventsource object itself.
However I couldn't find any such property, and since the "error"
events fired by both specifications are simple Events it doesn't
appear as if the information is exposed on the event object either.

Do neither of these specifications make error information available?

/ Jonas
Received on Tuesday, 4 October 2011 00:41:26 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:36 UTC