-
Notifications
You must be signed in to change notification settings - Fork 42
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
note that fragment directive is percent encoded using the standard percent encoded set #197
base: main
Are you sure you want to change the base?
Conversation
…rcent encoded set
This is concerning #194. |
I think I fixed the check, I got an account at the W3C: https://www.w3.org/users/139600 |
I sent an email to yoav to get this check cleared. (Hoping they can help). |
zamicol marked as non substantive for IPR from ash-nazg. |
characters](https://url.spec.whatwg.org/#utf-8-percent-encode). Characters in | ||
the [fragment percent encode | ||
set](https://url.spec.whatwg.org/#fragment-percent-encode-set) must be percent | ||
encoded. | ||
encoded. Fragment directive requires the more restrictive [percent encode | ||
set](https://url.spec.whatwg.org/#percent-encoded-bytes). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This refers to a "set" but links to instructions on how to percent encode/decode. Should we link instead to the scroll-to-text-fragment spec instead?
No description provided.