i thought the whole point of the <pre> tag was that markdown wouldn't try to murder it. why are you like this

dragon warrior iii for the game boy color describes me as "stubborn", and i'm tempted to agree with that assessment
co-owner tcrf.net. i run an old forum, jul.
i've been around the internet since '01.
i generally feel like the internet
peaked somewhere around '07.
private: @xkeeper-PLUS
18+: @xkeeper-TI
plural / some kind of digital therian thing.
still discovering myself.
all of this is new to me.
i thought the whole point of the <pre> tag was that markdown wouldn't try to murder it. why are you like this
excitingly this is due to something we had to hack in due to markdown's refusal to treat line breaks like people expect them to work in text, which when combined with our particular markdown parser has an unfortunate side effect that we mention in a footnote in the markdown help
note: one bug in embedded HTML handling is how we handle line breaks. if the starting tag of an HTML block is on the same line as text contained in it, line breaks inside the block will be preserved, instead of collapsed.
I can't figure out how to fix it. Keeping the tags to their own lines (so the preformat text isn't directly after <pre> or on the same line as its closing tag) doesn't seem to work. oh well
https://cohost.org/vogon/post/2361192-pre-font-f/2c9bbd14c99243eba94f89bc66c4517d
it seems to work for me, weird
idk if it's a preview thing or if it's because it's further wrapped in a <details> tag or if it only shows up after hitting post and not in the preview or what, but it doesn't seem to affect its functionality so wahtever
oh yep, wrapping the pre block in a details tag breaks everything
man I fucking hate markdown
This is why you should use code fences (triple-backticks, which I can't seem to get to appear correctly in comments) instead of injecting <pre> tags yourself.