Re: [whatwg/url] [Editorial] Guarantee that strings encoded with the component encode-set are valid opaque host strings. (#584)

@annevk commented on this pull request.



> @@ -205,7 +205,7 @@ U+0024 ($) to U+0026 (&), inclusive, U+002B (+), and U+002C (,).
 <p class=note>This is used by <cite>HTML</cite> for
 {{NavigatorContentUtils/registerProtocolHandler()}}, and could also be used by other standards to
 percent-encode data that can then be embedded in a <a for=/>URL</a>'s <a for=url>path</a>,
-<a for=url>query</a>, or <a for=url>fragment</a>. Using it with
+<a for=url>query</a>, or <a for=url>fragment</a>, and is also a <a>valid opaque-host string</a>. Using it with

```suggestion
<a for=url>query</a>, or <a for=url>fragment</a>, or <a for=/>opaque host</a>. Using it with
```
would be more consistent I think. I did notice while looking at this that valid opaque-host string doesn't say that `%` is fine. Perhaps the forbidden host code points should be two sets after all.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/pull/584#pullrequestreview-598265818