"additional CSS classes" makes inline code unreadable

[oliversturm]

I activated the "additional CSS classes" option because I wanted to add some JSON for custom classes. This worked fine, but then I found that inline code strings render piecemeal with the additional classes active, like this:

That's because various parts of the string are individually wrapped in spans that use the class cm-inlineCode.

Without the "additional CSS classes" option, there is just one span with this class:

...

Unfortunately this makes many of my notes quite unreadable because they have lots of inline code. For my purposes, I wouldn't even need these classes, but the custom classes I'm adding via JSON don't work if the option is disabled!

I think I will attempt to override cm-inlineCode in userchrome to use a colored background instead of the border settings it has by default. However, I think it would be better if there was an encapsulating element that can be styled, instead of the sequence of side-by-side elements which are created right now.

[CalebJohn]

The individual encapsulation is a by-product of the new built-in markdown editor in Joplin. If you opt-in to use the legacy editor it will be fixed (I think).

There are a few lingering inconsistencies that I have on my backlog, thanks for flagging this one I'll get it fixed for the next release.

[oliversturm]

An update, in case anybody else is reading - I have used a bit of CSS in userchrome.css to change the highlighting of inline code, so that the individual blocks can't be visually distinguished anymore. Might go back if this issue can be fixed, but the result isn't too bad.

.cm-inlineCode {
  background-color: lightyellow;
  border: none !important;
  border-radius: 0 !important;
  color: black !important;
}

[CalebJohn]

Looks like there is no (reasonable) fix for this. So I've added an extra bit of css so that the inline-code border is removed when using settings that cause it to break. The fix will be available in the next release.