sometimes in Markdown view there has some code before every notes how to sovle ?

[m11751]

Operating system

Windows

Joplin version

3.2.3

Desktop version info

Joplin 3.2.3 (prod, win32)

Client ID: afcea96aa0074a27a49d896f5cf32f4d
Sync Version: 3
Profile Version: 47
Keychain Supported: No

Revision: 1993d30

Current behaviour

every note in Markdown view have this code before:
Note viewer body { overflow: hidden; } #joplin-container-content { /* Needs this in case the content contains elements with absolute positioning / / Without this they would just stay at a fixed position when scrolling / position: relative; overflow-y: auto; padding-left: 10px; padding-right: 10px; / Note: the height is set via updateBodyHeight(). Setting it here to 100% / / won't work with some pages due to the position: relative / } #rendered-md { / This is used to enable the scroll-past end behaviour. The same height should / / be applied to the editor. */ padding-bottom: 400px; } .mark-selected { background: #CF3F00; color: white; } ul ul, ul ol, ol ul, ol ol { margin-bottom: 0px; }

Expected behaviour

solve this bug, thanks!

Logs

No response

[yash-writes-code]

hi, does this happen automatically for you,
everything seems to be working fine for me

can you please elaborate

[m11751]

hi, does this happen automatically for you, everything seems to be working fine for me

can you please elaborate

This problem doesn't always occur, it just happens occasionally. I asked gemni AI getting the answer below:
The error you're seeing in Joplin on Windows 11, which includes the code snippet:

CSS

Note viewer body { overflow: hidden; }
#joplin-container-content {
position: relative;
overflow-y: auto;
padding-left: 10px;
padding-right: 10px;
}
is not actually an error message in the traditional sense. It's the CSS code that Joplin uses to style the note viewer. This code is being displayed directly in your notes, which is the problem.

Here's a breakdown of why this happens and how to fix it:

Reason:

This issue usually arises due to a conflict or bug related to how Joplin renders or parses certain Markdown content, particularly when it involves HTML or CSS. It's been reported in the Joplin community before (as seen in the search results). The core issue is that this styling code, intended for the note viewer itself, is somehow being injected into the note content as plain text.

Solutions:

Update Joplin: The most straightforward solution is to ensure you're running the latest version of Joplin. Bugs are often fixed in newer releases. Check for updates within the Joplin application or download the latest version from the official Joplin website.

Check for Conflicting Plugins or Custom CSS: If you're using any Joplin plugins or have applied custom CSS through userchrome.css or userstyle.css, these could be interfering with the rendering process. Try temporarily disabling plugins or removing custom CSS to see if the issue resolves. If it does, re-enable them one by one to identify the culprit.

Inspect the Note Content: Carefully examine the Markdown content of the affected notes. Look for any unusual HTML tags, inline styles, or CSS code blocks that might be causing the problem. Sometimes, even seemingly innocuous HTML can trigger rendering issues. If you find any, try removing or correcting them.

Recreate the Note (if possible): If the issue is isolated to a few notes, try copying the content of the affected notes and creating new notes with that content. This can sometimes resolve underlying formatting issues.

User CSS workarounds (Advanced): If the problem persists and you're comfortable with CSS, you can try adding some CSS to your userstyle.css to hide the unwanted code. However, this is more of a workaround than a true fix. You could try something like this:

CSS

div.codeblock { /* Or a more specific selector if needed */
display: none;
}
This would hide any

elements with the class "codeblock." You'll need to inspect the HTML source of the rendered note (using your browser's developer tools if needed) to find the appropriate CSS selector to target the unwanted code.

Important Note: The issue you're encountering is likely a bug or a rendering quirk within Joplin. The provided solutions are aimed at mitigating the problem. If the issue persists after trying these steps, it's recommended to report the bug on the Joplin GitHub repository or the Joplin forum, providing as much detail as possible (including the Joplin version, operating system, and steps to reproduce the issue). This will help the Joplin developers to identify and fix the root cause.