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 27472 - RSAHashedKeyGenParams vs. Dictionary Fields Editorial Note
Summary: RSAHashedKeyGenParams vs. Dictionary Fields Editorial Note
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-11-30 21:21 UTC by Harry Halpin
Modified: 2016-05-23 23:45 UTC (History)
2 users (show)

See Also:

Attachments

Description Harry Halpin 2014-11-30 21:21:07 UTC 
Just double-checking this editorial note I just removed from CR - I was under impression it was addressed by dictionary fields.

---
From Section 20.8: 
              Should this be folded into RsaHashedKeyGenParams and rely on the optional nature of the  dictionary fields?
Comment 1 Harry Halpin 2014-11-30 21:24:52 UTC 
Another Editorial Note removed pre-CR. This seems like syntactic sugar and thus not a substantial change, but we don't want to forget about it. From 20.8

Editorial note

                  TODO: Specify the mapping between key.algorithm.hash and the appropriate Hash functions (and back to OID).
Comment 2 Mark Watson 2016-05-23 23:45:22 UTC 
Moved to https://github.com/w3c/webcrypto/issues/41