-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Text isn't properly formatted in certain situations #7
Comments
@reallyely The first issue bold formatting with links, I am still trying to find a way to fix that one. So it will be fixed sooner or later. For now try to not use bold formatting for links yet. For the second issue, I will fix that in 1.1.1, what you suggests makes perfect sense. Thanks for reporting! |
@bennyxguo I think I fixed this using .cm-strong:not(.cm-hmd-barelink):not(.cm-hmd-internal-link):not(.cm-highlight),
strong {
-webkit-background-clip: text;
-webkit-text-fill-color: transparent;
padding: 0 0.1rem;
color: #7aa2f7;
background-color: #7aa2f7;
background-image: linear-gradient(62deg, #87c2fd 0%, #dcb9fc 100%) !important;
} I just exclude |
Still reproduced on Linux. |
I'm super new to CSS but believe I found a fix for bold link issues! The exact issue I had was that if links were also bold, their text would not be rendered until hovered over. In
Bold links now display bold text styling correctly and still have their thick underline that grows and shrinks, and the text colour becomes white when hovered over. @iacore I'm running the native version of Obsidian on Garuda Linux, and this worked for me! Hope this helps someone!! 💜 |
@empressabyss you can send a PR with the changes if you want.
|
Great theme! Thanks for your hard work.
Windows 10, Obsidian 0.9.11, Obsidianite (Dark and Light Mode)
Two Issues I've run into so far
When a link is also bold, the text clipping appears to be unset.
Italicized text is forced to Operator Mono, but should fall back to Rubik as it's the free and recommended default font on your readme.
The text was updated successfully, but these errors were encountered: