Clarify how URL strings map to URL getters via table

[annevk]

Helps with #337.

---

Preview | Diff

[domenic]

I think omitting origin and host removes most of the value of such a table, unfortunately. Those are the confusing cases where an example is most helpful.

[annevk]

I suppose I could see how wide the table gets. Where would you put them? Or are you thinking about the multiple rows approach? (I didn't really like how that ended up looking.)

[domenic]

I was thinking of the multiple rows approach. It's pretty common, e.g. something like it (in ASCII form) appears even in the RFCs.

[annevk]

https://tools.ietf.org/html/rfc3986#section-3 seems to be a table with the heading row in the middle, but doesn't have multiple heading rows, or is there another one I missed?

Anyway, I think someone else might have to take this then and figure out an aesthetic that works. The table form looked rather weird to me and having to use multiple tables for multiple examples seemed like a bit of an abuse of tables as well.

[domenic]

You're right, that's the one that I was thinking of.