Join GitHub today
Web crypto support information for MS Edge #2738
@wiml , thanks for this PR!
As I understand things, the MS doc you referenced says that Edge does not support any of the following cryto primitives: RSA-PSS, ECDSA, ECDH, AES-CTR, SHA-1, HKDF, PBKDF2.
This PR handles that by listing all the primitives at the top level (as a note on SubtleCrypto), then just marking each of the individual APIs (e.g.
decrypt etc) as partially supported.
The problem I can see here is that say I'm on the page for
sign(), I can see it says partially supported, but I don't know what that means. I could only find out by going up to the main page for SubtleCrypto, but that's not obvious.
So I think it would be more helpful to note the crypto primitive limitations explicitly for each API item. Note that not all primitives are applicable to all APIs of course, so for example with
sign() only RSA-PSS and ECDSA need to be noted as unsupported in Edge. The spec has a table that's very helpful for sorting this out.
Once you do that, you don't need to list them at the top level at all, IMO. The table on the SubtleCrypto page will include all the individual APIs anyway. Marking it partial at the top level is still a good idea though probably.
For worker support, IMO you can just note that at the top level. Maybe it's worth noting at the API items but I don't think so really. But I also asked whether there's a standard or conventional way to describe this in BCD.
What do you think?
Thanks for the updates, much clearer! I had a few comments on a couple of details, I might have misunderstood some of the changes so please let me know if you don't agree.