Re: [whatwg/url] Editorial: fold cannot-be-base-URL into path (#655)

@TimothyGu commented on this pull request.

I really like this cleanup! It would also match how Go's net/url package stores paths better, and convergence is always nice.

>  
-<p class="note no-backref">A <a lt="is special">special</a> <a for=/>URL</a> always has a
-<a for=list lt="is empty">non-empty</a> <a for=url>path</a>.
+<p class=note>A <a lt="is special">special</a> <a for=/>URL</a> always has a
+<a for=url>hierarchical path</a>.

Can we define "hierarchical path` near here? This is quite awkward to read otherwise, since one would have to jump to another section.

> @@ -1404,9 +1396,12 @@ not a <a>special scheme</a>.
 <a for=url>username</a> or <a for=url>password</a> is not the empty string.
 <!-- also used by Fetch -->
 
+<p>A <a for=/>URL</a> has a <dfn export for=url>hierarchical path</dfn> if its <a for=url>path</a>
+is a <a for=/>list</a>.

What do you feel about defining "opaque path" as the opposite case, if the URL's path is a string?

-- 
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/655#pullrequestreview-774101531