This is a weird one.
I’m toying with a /now page and if I try to make an ordered list inside the --- Now --- block, when the page is rendered a <ul class="fa-ul"> gets created just inside <main> and wrapping everything.
This seems…very strange?
Can anyone else replicate this so I know I’m not losing my mind?
ETA: My dumbass use case is that I wanted some non-icon’d lists, so I was going to use <ol> with some css of list-style-type: disc; but as soon as I added an ordered list the above weirdness happened.
Alternatively, for the regular unordered lists is there some sort of magic {tag} that will tell the page generator, “Don’t put an icon on here just act like a normal unordered list?”
You’re not losing your mind! I was able to replicate it just now, but I’m not 100% able to explain it. The code that tries to do clever things with list and icons is in need of an overhaul. I think I was able to fix the issue with ordered lists. As for preventing icons, if you use an unordered list with HTML instead of Markdown, that should prevent the icons from appearing. For example:
<ul>
<li>Item 1</li>
<li>Item 2</li>
<li>Item 3</li>
</ul>
It still gets confused when I do it. I’ll just use the manual <ul> for now.
Oh actually. I guess I thought you could mix HTML and markdown, but if I put markdown links in the <li> the markdown just appears raw. Heh.
Yeah, you can mix HTML and Markdown within the same document, but not within the same line of the document (or at least not consistently). I’ve also found that weird things can happen when blocks of HTML and Markdown “touch” — you kind of have to space them out with a solid empty linebreak between them or things get wacky. (To be clear, this isn’t just a fluke of my genuinely flukey code, but is actually something that happens with a ton of Markdown parsers in general.)
I do think I can make this better in the long-term, though, by rewriting the overall parser to accept more specific directives for lists. Part of the problem now is that the current parser assumes that all Markdown unordered lists should be Font Awesome lists, which clearly isn’t always going to be the case. So instead of making that assumption, I can add something that lets you explicitly define what you want (or don’t want).
Maybe something like:
~ icon list
- Dog
- Cat
- Bird
Or
~ regular list
- Over
- Under
- Through
I’m tagging this post as a feature-request so I can keep track of this. 