Upgrade of Joplin client to v1.8.5 does not respect previous CSS settings

[markrenier]

After upgrading to v1.8.5, my previous CSS settings are not respected. I'm not sure if I need new CSS settings or if this is a bug.

This is my userchrome.css, which is the result of a previous issue (resolved here in this forum, thanks!) where I wanted the text side of the note to appear in a fixed width font, throughout Joplin, while the rendered side of the note appears as it does normally.

UserChrome.css begin ====
/* 
file: userchrome.css 
purpose: For styling the entire Joplin app (except the rendered Markdown, which is defined in `userstyle.css`) 
tested on: Joplin version 1.1.4, Y700

div.CodeMirror-lines * {
	font-size: 13px !important;
	color: black !important;
	font-weight: normal !important;
	text-decoration: none !important;
}

div.CodeMirror-lines * {
	font-size: 13px !important;
	font-weight: normal !important;
	text-decoration: none !important;
}
*/

/* CSS for the Dark theme to make the CodeMirror editor mimic the scheme of the old ACE editor */

span.cm-header {
    color: #CF6A4C;
    font-size: inherit !important;
    }

span.cm-link-text, span.cm-strong, span.cm-em {
    color: #8F9D6A !important;
    font-style: normal;
    font-weight: normal;
    }

span.cm-variable-2, span.cm-hr {
    color: #F9EE98 !important;
    }

span.cm-meta, span.cm-property {
    color: #7587A6 !important;
    }

 span.cm-string.cm-url {
    color: #DDDDDD !important;
    }

span.cm-comment {
    color: #DAD085 !important;
    }


UserChrome.css end ====

Joplin 1.8.5 (prod, win32)
Client ID: 348634c19a984fbc80460ee0b23c7d45
Sync Version: 2
Profile Version: 35
Keychain Supported: Yes
Revision: b28f087bb

I am using the internal editor.

[uxamanda]

FWIW, I haven't had any issues with my CSS persisting between upgrades – specifically I am on 1.8.5 with the same CSS as 1.8.4. My usual process is to perform a backup and then let overwrite the existing app which keeps the CSS in place, but I'm on a Mac so I am sure it is different.

Are you saying that with the upgrade that your CSS is no longer in the userchrome file or that it is no longer working?

Also, my file name is userchrome.css (lowercase), just in case that is causing an issue?

[markrenier]

I upgraded like I normally do: Shut down Joplin, run the install EXE, close the "run Joplin?" message, then manually restart the app. The file name is definitely userchrome.css, all lower case.

[dpoulton]

Your userchrome.css file does not appear to set any fonts so I guess the style of font is still coming from the app settings.

In the latest releases / pre-releases of Joplin (1.8.x) the font settings options have changed.

If you want the editor body text to be monospace you now have to set a monospace font. Otherwise it defaults to proportional. In the screenshot you can see the new settings options. I, like you, wanted monospace for both the editor body text as well as any code / tables / checkboxes in the editor, so you can see that I set the font twice.

[markrenier]

Thanks, dpoulton, that was the solution!