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

WebApps-ISSUE-182 (OperationNotAllowed): File API introduces a new OperationNotAllowed exception where other specs have an error code [File API]

From: Web Applications Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 06 Jun 2011 20:33:04 +0000
To: public-webapps@w3.org
Message-Id: <E1QTgTw-0001to-2h@stu.w3.org>

WebApps-ISSUE-182 (OperationNotAllowed): File API introduces a new OperationNotAllowed exception where other specs have an error code [File API]

http://www.w3.org/2008/webapps/track/issues/182

Raised by: Adrian Bateman
On product: File API

The File API adds an OperationNotAllowed exception with a single NOT_ALLOWED_ERR code. [1] Other specs, such as IndexedDB, include NOT_ALLOWED_ERR as one code within their existing exception object. [2]

We'd prefer to avoid the overhead of creating a new type just for this error and instead add NOT_ALLOWED_ERR as a new code to the existing object in the spec.

[1] http://dev.w3.org/2006/webapi/FileAPI/#not-allowed-error
[2] http://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html#widl-IDBDatabaseException-NOT_ALLOWED_ERR
Received on Monday, 6 June 2011 20:33:05 GMT

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