We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From EKR: https://lists.w3.org/Archives/Public/public-webrtc/2017May/0166.html
Is there any valid reason to allow the protocol to be a DOMString as opposed to ASCII or LDH? It's about to be shoved into a URL...
The text was updated successfully, but these errors were encountered:
In terms of WebIDL types, we only have DOMString, ByteString and USVString.
Sorry, something went wrong.
protocol can only contain ASCII
5c3f6b3
Fix for Issue #1293
RFC 3986 defines the syntax. As noted in Section 2.3, unreserved characters include ALPHA / DIGIT / "-" / "." / "_" / "~"
aboba
No branches or pull requests
From EKR: https://lists.w3.org/Archives/Public/public-webrtc/2017May/0166.html
Is there any valid reason to allow the protocol to be a DOMString as
opposed to ASCII or LDH? It's about to be shoved into a URL...
The text was updated successfully, but these errors were encountered: