-
Notifications
You must be signed in to change notification settings - Fork 59
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
[SecureContext] not defined by old WebIDL reference #232
Labels
Comments
dontcallmedom
added a commit
to dontcallmedom/webcrypto
that referenced
this issue
Jan 30, 2020
To facilitate maintenance of the spec Note the following normative changes were made as a mechanical result: * a number of unused normative references no longer appear: NIST SP 800-38B, NIST SP 800-56A, X9.62 * references to HTML & DOM have been moved to WHATWG documents (close w3c#229) * reference to WEBIDL has been moved to the editor draft as needed for refering to SecureContext (close w3c#232) In addition: * some of the information about dictionary members were moved from IDL comments to prose to enable preserving the existing ids * unused informative references no longer appear: CDSA, CNG, CryptoAPI, DRAFT-TLS-OBC, FileAPI, PKCS11 All ids of terms specifically defined by this spec (rather than re-defined for internal anchoring) have been preserved. Conversely, definitions that were merely import from other specs have been replaced by direct links to the said spec.
dontcallmedom
added a commit
to dontcallmedom/webcrypto
that referenced
this issue
Jan 30, 2020
To facilitate maintenance of the spec Note the following normative changes were made as a mechanical result: * a number of unused normative references no longer appear: NIST SP 800-38B, NIST SP 800-56A, X9.62 * references to HTML & DOM have been moved to WHATWG documents (close w3c#229) * reference to WEBIDL has been moved to the editor draft as needed for refering to SecureContext (close w3c#232) * a reference to RFC8174 has been added (as per ReSpec default behavior) In addition: * some of the information about dictionary members were moved from IDL comments to prose to enable preserving the existing ids * unused informative references no longer appear: CDSA, CNG, CryptoAPI, DRAFT-TLS-OBC, FileAPI, PKCS11 All ids of terms specifically defined by this spec (rather than re-defined for internal anchoring) have been preserved. Conversely, definitions that were merely import from other specs have been replaced by direct links to the said spec.
dontcallmedom
added a commit
to dontcallmedom/webcrypto
that referenced
this issue
Jan 30, 2020
To facilitate maintenance of the spec Note the following normative changes were made as a mechanical result: * a number of unused normative references no longer appear: NIST SP 800-38B, NIST SP 800-56A, X9.62 * references to HTML & DOM have been moved to WHATWG documents (close w3c#229) * reference to WEBIDL has been moved to the editor draft as needed for refering to SecureContext (close w3c#232) * a reference to RFC8174 has been added (as per ReSpec default behavior) In addition: * some of the information about dictionary members were moved from IDL comments to prose to enable preserving the existing ids * unused informative references no longer appear: CDSA, CNG, CryptoAPI, DRAFT-TLS-OBC, FileAPI, PKCS11 All ids of terms specifically defined by this spec (rather than re-defined for internal anchoring) have been preserved. Conversely, definitions that were merely import from other specs have been replaced by direct links to the said spec.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
While writing tests for this specification, I noticed that it uses the [SecureContext] attribute, but that is not defined.
This specification references an old version of WebIDL at https://www.w3.org/TR/WebIDL-1/ but [SecureContext] is not defined there.
[SecureContext] is defined in the newer version of WebIDL at https://heycam.github.io/webidl/
I suggest updating your WebIDL reference to point to a newer version of WebIDL.
Kind regards,
Jon
The text was updated successfully, but these errors were encountered: