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 22638 - Unreferenced "S.result"
Summary: Unreferenced "S.result"
Status: RESOLVED FIXED
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: 2013-07-10 20:16 UTC by Eric Roman
Modified: 2013-07-22 19:13 UTC (History)
1 user (show)

See Also:

Attachments

Description Eric Roman 2013-07-10 20:16:59 UTC 
14.2.1. The encrypt method
14.2.2. The decrypt method
14.2.3. The sign method
14.2.4. The verify method
14.2.5. The digest method

All include a step:
  (3) S.result = null.

I don't believe this is correct, as the result is delivered through the Promise and not through the CryptoOperation.
Comment 1 David Dahl 2013-07-10 21:38:45 UTC 
(In reply to comment #0)
> 14.2.1. The encrypt method
> 14.2.2. The decrypt method
> 14.2.3. The sign method
> 14.2.4. The verify method
> 14.2.5. The digest method
> 
> All include a step:
>   (3) S.result = null.
> 
> I don't believe this is correct, as the result is delivered through the
> Promise and not through the CryptoOperation.

I think the S.result = null referring to the internal state of the object that the implementation should handle. Is that correct Ryan?
Comment 2 Ryan Sleevi 2013-07-22 19:13:39 UTC 
Resolved in https://dvcs.w3.org/hg/webcrypto-api/rev/1907b69982c7

This is handled by the resolve/reject semantics.

.resolve() will always be some form of positive value/indicator
.reject() will either be 'null' or an appropriate DOMError , pending the discussion at http://lists.w3.org/Archives/Public/public-webcrypto/2013Jun/0003.html