Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Double brackets in footnotes
While typing the initial draft of a post, or editing an existing post, footnotes appear in the preview in superscript in square brackets, like this:
However, after saving the post, the footnotes appear in superscript in double square brackets, like this:
Am I correct in assuming that the double square brackets are unintentional, and that the appearance in the preview during editing is the desired format?
- A recent answer on Scientific Speculation that shows the double square brackets
- An older answer here on Meta that shows the single square brackets
An older question here on Meta that shows the single square brackets
- Shortly after I included this link, the question was edited. The edit was only to add a tag, but the footnote now shows double square brackets. This adds evidence that the bug affects posts that were posted or edited after a certain date.
- Use of a footnote in this Meta question for contrast
(Note that the functionality is working fine - clicking on the superscript footnote label takes you to the footnote, and clicking on the return link at the end of the footnote takes you back to where you were reading - in both preview and saved post.)
A footnote as an example (this showed above with single square brackets in the edit preview) ↩︎
This should be fixed now, but it's complicated and I'm just going to quote a bit from the pull request:
Note: This will result in footnotes that currently only have one pair of brackets having none. Unfortunately, this is an inconsistency in the HTML itself which cannot be corrected except by editing. I believe that this is because in the past, we had inconsistency in whether the server-side or client-side code would render post's to markdown, as has been noted before. Since we have moved to client-side rendering, inconsistencies should no longer be an issue going forward.
1 comment thread