Footer link href drops URL fragment (#anchor) — query string is kept but hash is stripped

[howdy39]

When a footer link in docs.json (footer.links[].items[].href) contains a URL fragment (e.g. #ai), the fragment is stripped from the rendered link. The query string on the same URL is preserved, but the hash is dropped. As a result, the link cannot deep-link to an on-page anchor on the destination site.

Expected behavior

The href is documented as type string (uri), and a fragment is a valid URI component (RFC 3986). The full URL — including its fragment — should be passed through unchanged to the rendered <a href>.

Actual behavior

The fragment is removed. The query string survives, so the result is asymmetric:

docs.json value	Rendered href
https://example.com/terms?foo=true#ai	https://example.com/terms?foo=true
https://example.com/terms#ai	https://example.com/terms

In both cases #ai is gone.

Steps to reproduce

1. Add a footer link with a fragment to docs.json:

"footer": {
  "links": [
    {
      "header": "Terms",
      "items": [
        { "label": "AI terms", "href": "https://example.com/terms?foo=true#ai" }
      ]
    }
  ]
}

2. Run mint dev and open the local prev
3. Inspect the rendered footer link (or the embedded docsConfig JSON in the served HTML).

Observed result

In the embedded docsConfig of the served page, the value is already normalized to:

"href":"https://example.com/terms?foo=true

The fragment is gone before render, so this looks like it happens during config parsing/normalization rather than
at the DOM level.

Environment

• mint : 4.2.632
• Node.js: v24.17.0
• Reproduced in local preview (mint dev

Notes

The inconsistency (query string preservedan unintended side effect of URL