pull down to refresh

100 sats \ 2 replies \ @sox 5h \ parent \ on: Stacker Saloon

Footnote definitions are ordered in a dumb-ish way, basically a comes after the 4 lol

I didn't want to implement footnotes with anything other than numbers because it felt weird... but at the same time footnote references should not allow non-numeric values to be considered references.

What made the footnote definitions' implementation trivial is the fact that it's a normal numeric ordered list with normal list items

write
preview
150 sats \ 1 reply \ @optimism 5h

Yeah that's a behavior change from before, doesn't have to be a bug per se.

[^😭][^a][^4][^3] would previously display as [1][2][3][4] and correspond to the numbered list in the footer as

----
1. ...
2. ...
3. ...
4. ...

the only issue right now is that a displayed [😭] corresponds to item 1 in the list, except there is no way to tell other than by the #fn-<x> and #fnrev-<x> in the urls.

Edit: perhaps not parsing non-numericals (and forcing us to order them manually) is the easy solution, or the hard mode otherwise, replacing the <ol> with a <ul> and parsing the ref from the [^definition]:?

reply
100 sats \ 0 replies \ @sox 4h
replacing the

<ol>

with a

<ul>

and parsing the ref from the [^definition]:?

This can work 👀

edit: hey a bug! inline code in block quotes is ignored lol

reply