spec inconsistency wrt forward slash after host if there's no path ?

[o0Ignition0o]

As mentioned in my WIP pull request ( #523 ) I'm a bit confused wrt the forward slash uri parsing when there's no path :

a port setter test
seems to be inconsistent with a protocol setter test
There doesn't seem to be any consistency in WPT wrt the "/" when there is no path.
The specification seems to dismiss '/' at the end if there is no path:
" Otherwise, then for each string in url’s path, append U+002F (/) followed by the string to output."

Does anyone have any pointers on how I'm supposed to handle it ?

[SimonSapin]

It’s possible that the spec has changed but the code has not code up yet. See #163 and #290.

@nox I think you mentioned something about empty paths? (Without even the initial slash)

[o0Ignition0o]

Ok I may want to actually rollback my changes, and apply each patch separately, to make sure I don't get lost in the proces, thank for your reply :)