Document base URL does not conform to RFC3986 re. fragment identifiers

[namedgraph]

What is the issue with the HTML Standard?

I was surprised to see that the baseURI property in Chrome returns URLs that include a fragment identifier.

I think it should be specified that document base URL should not include the fragment identifier.

This is because RFC3986 5.1 states:

A base URI must conform to the <absolute-URI> syntax rule (Section 4.3). If the base URI is obtained from a URI reference, then that reference must be converted to absolute form and stripped of any fragment component prior to its use as a base URI.

[annevk]

Browsers implement https://url.spec.whatwg.org which has no such rule. In particular a base URL is just a specially designated URL, that's it. There are certain places where we serialize without fragment identifier, but baseURI is not one of those places.

[namedgraph]

How is it a "base URL" if it cannot be used as a base URL for resolution of relative URLs? I don't see resolution defined in the WHATWG spec.

[annevk]

The web platform doesn't have a relative URLs as a concept, only as string inputs for the URL parser (which also takes a base URL).

[namedgraph]

Sorry, I cannot take the WHATWG specs seriously.

[annevk]

Okay. Meanwhile this seems invalid, so I'll close.