Skip to content
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

Clarify DOMString comparison method in dictionaly WebTransportHash #413

Closed
himorin opened this issue Aug 22, 2022 · 0 comments · Fixed by #453
Closed

Clarify DOMString comparison method in dictionaly WebTransportHash #413

himorin opened this issue Aug 22, 2022 · 0 comments · Fixed by #453
Labels
Discuss at next meeting Flags an issue to be discussed at the next WG working i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@himorin
Copy link

himorin commented Aug 22, 2022

5.9 Configuration, verify a certificate hash
https://www.w3.org/TR/2022/WD-webtransport-20220623/#verify-a-certificate-hash

3.1.2 of operation states:

If algorithm of hash is equal to "sha-256", and hashValue is equal to referenceHash, the certificate is valid. Return true.

User supplied value (via constructor of interface WebTransport within WebTransportOptions) is compared with spec defined value as is equal to, but this text is not clear how to compare by equal.
This part should use defined term(s) in INFRA and refer there, like is or is identical to or is an ASCII case-insensitive match

@himorin himorin added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label Aug 22, 2022
@wilaw wilaw added the Discuss at next meeting Flags an issue to be discussed at the next WG working label Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discuss at next meeting Flags an issue to be discussed at the next WG working i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants