22571 2013-07-04 01:07:53 +0000 Invalid IDL - Dictionary members as attributes 2014-02-13 12:56:25 +0000 1 1 1 Unclassified Web Cryptography Web Cryptography API Document unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 sleevi sleevi ap chris israelh oldest_to_newest 90312 0 sleevi 2013-07-04 01:07:53 +0000 Both the Key object and the CryptoOperation object expose dictionary attributes - 'algorithm' Per http://dev.w3.org/2006/webapi/WebIDL/#idl-attributes , attributes MUST NOT be sequences, dictionaries, or union types that have dictionaries or sequences as members. One way to resolve this is to specify parallel interfaces for normalized algorithms. 100521 1 sleevi 2014-02-13 12:56:25 +0000 I've hopefully resolved this in https://dvcs.w3.org/hg/webcrypto-api/rev/2fa3494f0179 The Key object now exposes a KeyAlgorithm interface, rather than the Algorithm dictionary, and each of the Key types is meant to specify their minimal set of common parameters. For example, an RSA key (whether public or private) includes the algorithm name, the public modulus length (in bits), and the public exponent. For algorithms which are 'tainted' - eg: by hash algorithms, as in the case of PSS, SSA, and OAEP - additional properties - such as the Hash - are exposed. There are still gaps in the normative requirements to specify exactly how to convert an Algorithm to a KeyAlgorithm, but hopefully this resolves the blocking concern. As such, I'm marking this as FIXED.