• Pamasich@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year ago

    So, slight correction to my previous post (which I now deleted) thanks to @troplin.

    It seems that phrasing content like <span> elements are allowed inside <pre> elements according to the spec, so Lemmy is actually doing the right thing there. It's on kbin to fix this, not Lemmy.

    I commented on one of the closed issues about this on the kbin code repository, asking for the issue to be reopened. Hopefully it will so this gets fixed, I'm not sure though how visibility works if the issue is already closed. I'll make a new one if it's neither reopened nor replied to until next week, if no one else does first.

      • Pamasich@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        You're right, I only read the beginning of article, the Mozilla docs also mention the phrasing content later on the same page.

        Guess it's really on kbin then to fix this.

  • adam@kbin.pieho.me
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    The issue here is that Lemmy is federating out it's content with the pre blocks containing rendered code fit for some sort of code display plugin/CSS - which KBin doesn't have.

    It would ideally send out the blocks html encoded and would let downstream implementations like KBin or others figure out how to display it themselves. I don't know how we would fix this.