WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2025 Poal.co

106

(post is archived)

[–] 0 pt

I've just downloaded the page, turned the wifi-killswitch, and loaded the page into the Firefox browser, and had the same issue. So I think, that it's a firefox issue.

[–] 0 pt

Of course, my firefox also has some privacy protections enabled. So it may also be a privacy-protection issue.

[–] 0 pt

Downloading the page from Torbrowser will save the broken markdown.

You must use a direct page load from another browser.

[–] 0 pt

Plus: The way <code> is rendered is ugly. Just use the "Hack" font, and remove the background and change the color into something like #ccc

[–] 0 pt

User's Global CSS is there for those who don't like the default UI. Feel free to use it.

[–] 0 pt

I've fixed this as follows:

The <code> tag is one level below a <pre> tag. I've given the <pre> tag the following CSS attributes:

word-wrap: anywhere;
white-space: pre-wrap;

This fixed it for me. I'd suggest that you add those attributes to your CSS, because it seems that that's what you're expecting to happen, but apparently not all browsers act that way by default.

[–] 0 pt

<code> and <pre> are locked and using your browser's default user agent stylesheet. There's no need to modify them to accommodate a browser that doesn't support (for unknown reasons) them.

[–] 0 pt

And... The problem lies not in the HTML but in the CSS, which won't by changed if I download the whole page via torbrowser. Yeah, I understand, that this makes debugging harder on your side.

Anyways, add my two lines to the CSS under something like:

.content pre {}

or:

.content {
    pre {
    }
}

if you're using SCSS.

[–] 0 pt

that this makes debugging harder on your side.

There's no bug but a non-compliant browser on your side.

We have a sub for suggestions: