On Tue, 04 Oct 2011 00:59:18 +0200, Jonas Sicking jo...@sicking.cc wrote:
Yup. I do wonder if we should introduce a DOMError class which can be
reused in various cases which need APIs like this. IndexedDB could
also use it and I seem to recall that HTML5 does too.
I could certainly introduce a
On Mon, Oct 3, 2011 at 11:54 PM, Anne van Kesteren ann...@opera.com wrote:
On Tue, 04 Oct 2011 00:59:18 +0200, Jonas Sicking jo...@sicking.cc wrote:
Yup. I do wonder if we should introduce a DOMError class which can be
reused in various cases which need APIs like this. IndexedDB could
also
On 10/4/11 2:54 AM, Anne van Kesteren wrote:
On Tue, 04 Oct 2011 00:59:18 +0200, Jonas Sicking jo...@sicking.cc
wrote:
Yup. I do wonder if we should introduce a DOMError class which can be
reused in various cases which need APIs like this. IndexedDB could
also use it and I seem to recall that
On 9/30/11 9:46 PM, Adrian Bateman wrote:
Hi Arun,
Thanks for the follow-up - you beat me to it. We've been reviewing this in
the context of the other specs and, as Israel outlined for IndexedDB, we're
happy with the new WebIDL approach.
I think we should go ahead and migrate the File API
On Mon, Oct 3, 2011 at 11:51 AM, Arun Ranganathan a...@mozilla.com wrote:
On 9/30/11 9:46 PM, Adrian Bateman wrote:
Hi Arun,
Thanks for the follow-up - you beat me to it. We've been reviewing this in
the context of the other specs and, as Israel outlined for IndexedDB,
we're
happy with the
On 10/3/11 4:59 PM, Jonas Sicking wrote:
On Mon, Oct 3, 2011 at 11:51 AM, Arun Ranganathana...@mozilla.com wrote:
On 9/30/11 9:46 PM, Adrian Bateman wrote:
Hi Arun,
Thanks for the follow-up - you beat me to it. We've been reviewing this in
the context of the other specs and, as Israel
On 10/3/11 6:59 PM, Jonas Sicking wrote:
On Mon, Oct 3, 2011 at 3:35 PM, Arun Ranganathana...@mozilla.com wrote:
On 10/3/11 4:59 PM, Jonas Sicking wrote:
On Mon, Oct 3, 2011 at 11:51 AM, Arun Ranganathana...@mozilla.com
wrote:
On 9/30/11 9:46 PM, Adrian Bateman wrote:
Hi Arun,
Thanks for
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
On Mon, Oct 3, 2011 at 4:26 PM, Ian Hickson i...@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
On Mon, Oct 3, 2011 at 3:35 PM, Arun Ranganathan a...@mozilla.com wrote:
On 10/3/11 4:59 PM, Jonas Sicking wrote:
On Mon, Oct 3, 2011 at 11:51 AM, Arun Ranganathana...@mozilla.com
wrote:
On 9/30/11 9:46 PM, Adrian Bateman wrote:
Hi Arun,
Thanks for the follow-up - you beat me to it.
On Mon, 3 Oct 2011, Jonas Sicking wrote:
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,
On Mon, Oct 3, 2011 at 6:00 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 3 Oct 2011, Jonas Sicking wrote:
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
On Mon, 3 Oct 2011, Jonas Sicking wrote:
So MediaError is exactly the type of thing that I'm talking about that
we might want to move into the DOM4 spec. We have the same thing in the
File API spec. The FileError interface is just a plain object with a
single .code property. We're
Hi Arun,
Thanks for the follow-up - you beat me to it. We've been reviewing this in
the context of the other specs and, as Israel outlined for IndexedDB, we're
happy with the new WebIDL approach.
I think we should go ahead and migrate the File API exceptions to this new
model and use ISSUE-182
14 matches
Mail list logo
