Ehsan Akhgari wrote: > Can you please clarify what are the areas that we don't fully adhere to > the spec? Do we expect the fixes to those and potentially new spec > issues in the future to break backwards compatibility?
KeyAlgorithms were recently changed to dictionaries (from interfaces) and we did not get around to change that yet. Richard Barnes has a patch almost ready in bug 1037892 [1] though. We didn't have to change tests to make them work with KeyAlgorithm dictionaries so that change would not break existing code. We would probably aim to land it before enabling WebCrypto by default anyway. Other parts we're missing is import/export for some formats (e.g. PKCS8 for ECDH/DH) and we're missing a few algorithms completely. We only need more time to implement those but that wouldn't break any existing code either. - Tim [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1037892 > Thanks! > Ehsan > > On 2014-09-03, 1:36 PM, Tim Taubert wrote: >> As of September we intend to enable the WebCrypto API by default on all >> platforms. It has been developed behind the dom.webcrypto.enabled >> preference. >> >> Tracking bug: >> https://bugzilla.mozilla.org/show_bug.cgi?id=865789 >> >> Spec: >> https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html >> (A CR is planned soon, only smaller changes to the spec lately.) >> >> Reasoning: >> The implementation of the WebCrypto API has made lots of progress in >> Firefox 33+34. We added most of the basic functionality and algorithms, >> and should be mostly spec compliant. >> >> Chromium has had the WebCrypto API enabled by default since Crome 37, >> which was released in late June 2014. Their implementation supports a >> subset of the algorithms that we do, and has roughly the same level of >> spec compliance. We expect the two implementations to be mostly >> interoperable as-is, with some fine points being ironed out as the spec >> is finalized. >> >> We thus propose to enable the WebCrypto API by default for all platforms >> to get some more feedback from developers and give them the opportunity >> to use new functionality. >> >> - Tim >> _______________________________________________ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform >> > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
