When the authority is absent, the path is relative, and the path after RFC 3986 normalization result starts with //, then WHATWG URL Standard handles the path as "opaque" and does not touch it during normalization.
However, the current iri-string crate does not support "opaque" paths.
So, foo:.///bar is untouched by WHATWG URL Standard but is_normalized_whatwg() returns false for it.
Possibly I should not say or imply the normalization as compliant to "WHATWG URL Standard", and this method should have different name.
When the authority is absent, the path is relative, and the path after RFC 3986 normalization result starts with
//
, then WHATWG URL Standard handles the path as "opaque" and does not touch it during normalization. However, the current iri-string crate does not support "opaque" paths. So,foo:.///bar
is untouched by WHATWG URL Standard butis_normalized_whatwg()
returnsfalse
for it.Possibly I should not say or imply the normalization as compliant to "WHATWG URL Standard", and this method should have different name.
Related to #29.