Footnotes are matched case-insensitive, but links keep their casing, breaking them

Question

Footnotes are matched case-insensitive, but links keep their casing, breaking them

wooorm opened this issue 3 years ago · 1 comments

Take this example:

Some calls.[^A][^a][^ΑΓΩ][^αγω]

Lorem ipsum dolor sit amet [...8 paragraphs to observe whether linking works correctly]...  laborum.

[^A]: ALPHA

[^a]: alpha

[^ΑΓΩ]: ΑΓΩ

[^αγω]: αγω

(I’ll paste it later so the footnotes stay with the example)

Footnote calls and definitions are matched correctly: case-insensitive including proper unicode case folding, and first-definition-used (same as link references / link definitions).

However, the IDs on both the calls and the lis for each definition seem to use a case normalized (lowercase) form:

id="user-content-fn-a-7af09f7028a468bc0c764dcc21196dbe"
id="user-content-fnref-a-7af09f7028a468bc0c764dcc21196dbe"
id="user-content-fnref-a-2-7af09f7028a468bc0c764dcc21196dbe"

Whereas the hrefs use a case sensitive form:

href="#user-content-fn-A-7af09f7028a468bc0c764dcc21196dbe"
href="#user-content-fnref-A-7af09f7028a468bc0c764dcc21196dbe"
href="#user-content-fnref-A-2-7af09f7028a468bc0c764dcc21196dbe"

This seems to break at least on Chrome and Firefox for me.

Pasted example from above:

Some calls.¹¹²²

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

ALPHA ↩ ↩²
ΑΓΩ ↩ ↩²

Answer 1 · 2021-10-01T09:06:10.000Z

A similar problem exists for:

Call.[^a\b].

[^a\b]: y

Where the hrefs use %5C as percent encoding for the /. The IDs are lowercased to %5c.

Call.¹.

y ↩