-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CryptoKey global already practiced but not defined. #296
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Every single browser implementation attaches the CryptoKey constructor to window or worker global scope. This is very useful for defensive programming when building libraries / code around web crypto, e.g. to fail early on invalid user input (when key is not an
instanceof CryptoKey
and wanting to offer a useful and consistent error message (unlike the implementation specific ones that often come with no information whatsoever).I think https://w3c.github.io/webcrypto/#crypto-interface should get updated to reflect what's already the practice today and add CryptoKey alongside of the readonly
crypto
to WindowOrWorkerGlobalScope.The text was updated successfully, but these errors were encountered: