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 29359 - Make the "exceptions" section clearer
Summary: Make the "exceptions" section clearer
Status: RESOLVED MOVED
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-05 19:09 UTC by Boris Zbarsky
Modified: 2016-05-24 00:37 UTC (History)
2 users (show)

See Also:

Attachments

Description Boris Zbarsky 2016-01-05 19:09:03 UTC 
The text in http://www.w3.org/TR/2014/CR-WebCryptoAPI-20141211/#SubtleCrypto-Exceptions is not exactly clear to me.  Is it saying that whenever throwing OperationError the .message must be precisely the string "The operation failed for an operation-specific reason"?  Is it saying that the string is up to the UA?  Is it saying that it's up to the UA but if the UA has no idea then "The operation failed for an operation-specific reason" is a good default?  Something else?

I _think_ the intent is the "up to the UA but this may be a reasonable default" behavior, but that should just be spelled out if so.
Comment 1 Mark Watson 2016-05-24 00:37:23 UTC 
Moved to https://github.com/w3c/webcrypto/issues/84