Post B4ivt7qbjCAkDFBx6e by mirabilos@toot.mirbsd.org
 (DIR) More posts by mirabilos@toot.mirbsd.org
 (DIR) Post #B4hsaAT3Ghj3oeTyUq by jwo@mastodonczech.cz
       0 likes, 0 repeats
       
       @mirabilos, your bio is breaking layout of Mastodon. 🤣 (No, there is no horizontal scrolling. :D)
       
 (DIR) Post #B4hsaAeOaWneNpn2B6 by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @jwo Mastodon is a blight on the Fediverse, so… ce la vieh ;)Write a bugreport.You could also put…    pre {            overflow-x:scroll !important;    }… into ~/.mozilla/firefox/*/chrome/userContent.css, might help (I know I had to do that for Pinafore/Semaphore, the web clients I’m using).
       
 (DIR) Post #B4hu4AjExhtNGdvRdw by jwo@mastodonczech.cz
       0 likes, 0 repeats
       
       @mirabilos This is so minor (and funny) quirk that I even don't feel the need to file a bug report. :DBtw, didn't you leave a leading whitespace there? ;)
       
 (DIR) Post #B4hu4BER5iqUpOWMGe by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @jwo yeah, the whole line is just copied from my webpages, and the <head> is baseline indented one space.
       
 (DIR) Post #B4hu4BPmPXv5OZpPwu by jwo@mastodonczech.cz
       0 likes, 0 repeats
       
       @mirabilos Btw, Mastodon nests <code> in a <pre> there for some reason. Is that valid? Is that a recommended practice? (Is that another Mastodon quirk?) I've never seen that before.
       
 (DIR) Post #B4huCaRvDWCbM5pz7Y by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @jwo I’ve long wondered about it as well, and I checked, it apparently is valid, but I still don’t recall ever getting a satisfying explanation for this.I certainly don’t do it, just <pre> has always been enough.
       
 (DIR) Post #B4iv9J0zsJPVWlCdN2 by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @jwo heh, via https://unstable.systems/@jneen/116302498173795149 I found https://thedailywtf.com/articles/preformatted today, which did make me look them up.<pre> implies “keep whitespace” and “format fixed-width” and is a block-level element.<code> is an inline element that merely adds semantics, so it could be used for e.g. js syntax highlighters to mark where they should colourise. It does not imply monospace formatting.Both go back ways (HTML 3.2 had them).
       
 (DIR) Post #B4ivl4w0fqzqrUsikS by jwo@mastodonczech.cz
       0 likes, 0 repeats
       
       @mirabilos Yeah, I expect semantics like this and it makes sense, it just feels weird/unusual – and I've seen pretty much all possible inline markup inside <pre>, especially links or some styling. I just didn't expect <code> to be here.
       
 (DIR) Post #B4ivl5J3IBQc0xf7fE by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @jwo and especially paired like that, yeah…
       
 (DIR) Post #B4ivt7qbjCAkDFBx6e by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @jwo in this case it’s the Markdown renderer built into GotoSocial that’s doing this, btw, and I put full blame onto the Markdownistas for this. (Especially as they also do it for præformatted blocks that just do not contain any code, too.)