This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
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.