[Bug 27598] New: Clarification: Can NotSupportedError be thrown in places where the spec uses an OperationError?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27598

            Bug ID: 27598
           Summary: Clarification: Can NotSupportedError be thrown in
                    places where the spec uses an OperationError?
           Product: Web Cryptography
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Web Cryptography API Document
          Assignee: sleevi@google.com
          Reporter: ericroman@google.com
                CC: public-webcrypto@w3.org

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?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Friday, 12 December 2014 20:49:43 UTC