Timothy Gu

> Note also that `?` is not part of the `pathname` getter. Oops, an off-by-one. > In particular different schemes That does indeed sound like a nice idea. > You...

@EnnexMB Thanks for your interest in this. The WIP are unfortunately on my laptop that has seen some physical damage since the time I created them. I'll try to recover...

@EnnexMB Sorry about the delay, but yes! Here's the diff for the table version: https://gist.github.com/5eb111b5021b338d516e97225a65bed4 Here's the SVG if you're interested. Note the `search` coverage is still wrong. https://gist.github.com/bf539f420463bab1eb7426cff267a5b4 (drawing2.svg...

@EnnexMB Oops, I’m sorry to have missed your comment on the gist itself. What @annevk gave should work, though I would personally do this: 1. Put the gist file in...

See #24 on some previous work done on creating a formal grammar for URLs, perhaps displayed through railroad diagrams (see http://intertwingly.net/stories/2014/10/20/Url.xhtml). In my opinion, RR diagrams and formal grammar solve...

I mean, Chrome and Firefox don't even escape spaces (or anything not in the C0 controls set) in non-special paths…

@achristensen07 Are you okay with aligning Safari on this?

@achristensen07 would you be able to describe the algorithm that Safari uses for the protocol setter, including the reparse step?

I like the idea of ensuring the parts don't get reinterpreted too much before allowing a non-special URL to switch to a special scheme. As an example, to allow switching...

I'm personally pretty satisfied with @annevk's explanation, that the path and query are considered parts of the same thing (response from the server). If a user would really like to...