Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chore: Desktop: Markdown editor panes: Migrate from style properties to SCSS #11423

Conversation

personalizedrefrigerator
Copy link
Collaborator

@personalizedrefrigerator personalizedrefrigerator commented Nov 20, 2024

Summary

This pull request migrates part of the Markdown editor's styling from style=-based styling to SCSS.

Motivation: This is motivated in part by the complicated styling used here to style Joplin's editor/viewer panes. Such style sheets are likely to be fragile to changes to the app's HTML structure in the future.

Screenshots

CodeMirror 6-based editor

Screenshot: editor and viewer side-by-side
Screenshot: editor only
Screenshot: viewer only

Legacy editor (CodeMirror 5-based)

Screenshot editor and viewer side-by-side
Screenshot editor only
Screenshot viewer only

@personalizedrefrigerator personalizedrefrigerator changed the title Chore: Desktop: Migrate from style= to SCSS for visible note pane styling Chore: Desktop: Migrate from style properties to SCSS for visible note pane styling Nov 20, 2024
@personalizedrefrigerator personalizedrefrigerator changed the title Chore: Desktop: Migrate from style properties to SCSS for visible note pane styling Chore: Desktop: Markdown editor panes: Migrate from style properties to SCSS Nov 20, 2024
@laurent22 laurent22 merged commit 5dcbf4c into laurent22:dev Nov 20, 2024
7 checks passed
@dansmith65
Copy link

Thank you so much for this!

I use similar code in my userchrome.css as referenced in your motivation link. I was annoyed that a recent update broke that css again... then I was overjoyed to find so many more classes defined to allow for better targeting specific elements. So much so that I tracked down this pull request to thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants