Removed incorrect extra example for AES-CTR #42577
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Removed an incorrect extra example for AES-CTR encryption
Motivation
It is likely a leftover draft that doesn't have an equivalent in https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/decrypt and that doesn't follow the rest by not being based upon the full example code and that uses in window.crypto.subtle.encrypt's algorithm parameter a length of 128 instead of the recommended 64 according to https://developer.mozilla.org/en-US/docs/Web/API/AesCtrParams, it also uses window.crypto.getRandomValues and window.crypto.subtle.importKey to generate the key instead of just window.crypto.subtle.generateKey