ISSUE-182: File API introduces a new OperationNotAllowed exception where other specs have an error code
OperationNotAllowed
File API introduces a new OperationNotAllowed exception where other specs have an error code
- State:
- CLOSED
- Product:
- HISTORICAL: File API [this spec uses Bugzilla for all Bug and Issue tracking http://tinyurl.com/Bugs-FileAPI]
- Raised by:
- Adrian Bateman
- Opened on:
- 2011-06-06
- Description:
- 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 - Related Actions Items:
- No related actions
- Related emails:
- Re: [File API] Issue 182 about OperationNotAllowed (from arun@mozilla.com on 2011-10-03)
- Re: [File API] Issue 182 about OperationNotAllowed (from jonas@sicking.cc on 2011-10-03)
- Re: [File API] Issue 182 about OperationNotAllowed (from arun@mozilla.com on 2011-10-03)
- Re: [File API] Issue 182 about OperationNotAllowed (from jonas@sicking.cc on 2011-10-03)
- Re: [File API] Issue 182 about OperationNotAllowed (from arun@mozilla.com on 2011-10-03)
- RE: [File API] Issue 182 about OperationNotAllowed (from adrianba@microsoft.com on 2011-10-01)
- [File API] Issue 182 about OperationNowAllowed (from arun@mozilla.com on 2011-09-29)
- Re: [FileAPI] Updates to FileAPI Editor's Draft (from jonas@sicking.cc on 2011-06-08)
- Re: [FileAPI] Updates to FileAPI Editor's Draft (from robin@berjon.com on 2011-06-08)
- RE: Publishing an update of File API spec (from adrianba@microsoft.com on 2011-06-06)
- WebApps-ISSUE-182 (OperationNotAllowed): File API introduces a new OperationNotAllowed exception where other specs have an error code [File API] (from sysbot+tracker@w3.org on 2011-06-06)
Related notes:
The intent here is to introduce an exception that can be re-used across the platform.
In the example cited above with IndexedDB, the NOT_ALLOWED_ERROR pertains to a database operation that isn't allowed (or affiliated transactions -- the specification counsels a more specific error code to be used in lieu of this one).
But in the File API, we're using this exception for a "call-order" sequence on read methods that isn't allowed -- this differs from exceptions and errors that occur at the underlying file level, and has more to do with order of operations in an API.
In general, this exception seems useful.
So we can now safely close this, since the spec. now uses DOMError and DOMException, in keeping with both the new "throw" stipulations and the error event etc.
Arun Ranganathan, 1 Feb 2012, 16:28:39Display change log
