`api.SubtleCrypto` - Break out algorithm support

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

SubtleCrypto API data mixes partial_implementation and notes and subfeatures to show support for specific algorithms. This is inconsistent and, as a consumer, difficult to work with.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

It'd be nice if specific algorithms (such as ECDSA) were broken out into subfeatures like x25519 and ed25519 are.

Did you test this? If so, how?

N/A

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

web-features had to override BCD to reconcile our data with the way caniuse represents this information. See https://github.com/web-platform-dx/web-features/pull/3268/.

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto#browser_compatibility

MDN metadata

No response

Start with the SubtleCrypto browser-compatibility data and compare its current partial_implementation, notes, and subfeature entries with the linked web-features pull request. Identify the algorithms that need separate subfeatures; done means algorithm support is represented consistently and consumers no longer need the cited override.