This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27598 - Clarification: Can NotSupportedError be thrown in places where the spec uses an OperationError?
Summary: Clarification: Can NotSupportedError be thrown in places where the spec uses ...
Status: RESOLVED MOVED
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-12 20:49 UTC by Eric Roman
Modified: 2016-05-24 00:05 UTC (History)
2 users (show)

See Also:

Attachments

Description Eric Roman 2014-12-12 20:49:41 UTC 
There are some operational failures an implementation may have due to unsupported functionality.

For instance in Chrome:
  * Importing or generating 192-bit AES keys is not supported
  * Generating an RSA modulus < 256 bits or > 16384 bits is not supported
  * Generating an RSA key with publicExponent not one of {3, 65537} is unsupported

My reading of the spec suggests that each of these errors must be an OperationError.

However I feel that NotSupportedError is more appropriate.

Is a confirming user agent allowed to throw NotSupportedErrors in places not explicitly mentioned by the spec?
Comment 1 Mark Watson 2016-05-24 00:05:21 UTC 
Moved to https://github.com/w3c/webcrypto/issues/62