-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Headings not properly sized #90
Comments
I'm facing the same issue. I do think its a compatibility issue with the theme and the new version. It would be great to tag it with bug label. |
Check #89 |
+1 to this. Tried the fix in #89 with little luck. |
I have the same issue. And I was unable to understand how to fix it with the #89. I'm not proficient using CSS. Someone can give us a clue. |
Hi @DenebAguirre Hope it helps! |
@yuconnorl thank you, it worked! |
Just switched to live preview and noticed the header changing size, only with this theme. Happy to see that there was already a fix floating around. Thanks for suggesting the fix in #89 as it worked as intended and thanks to @yuconnorl for the explanation for how to implement it! |
@yuconnorl thank you for the comment, this worked for me |
Hello,
I have been using the Yin and Yang theme for a few weeks now and it has been working great. Since yesterday, however, headings are suddenly no longer sizing properly in Live Preview mode. The headings are now very small, compared to their true size which used to be much larger before yesterday. Here is an example of one of my notes, with the first heading being level 1 (#) and the second heading level 2 (##):
As you can see, the headings are even smaller than the body text itself.
I suspect that this issue has to do with Obsidian Release v0.13.31. In the release notes, it even states that 'Fixed headings in legacy editor not properly sized.' However, I am not using legacy mode, and my headings are still broken even in version 0.13.31.
Is this related to the Yin and Yang theme or should I post on the Obsidian forums to find a solution? Does anyone else recognise this issue?
The text was updated successfully, but these errors were encountered: