fix: Tiptap editor and heading styles - #2041
Merged
Merged
Conversation
github-project-automation
Bot
moved this to 馃Л Planning evaluation (don't pick)
in 馃摑 Productivity team
silverkszlo
reviewed
Sep 2, 2025
silverkszlo
approved these changes
Sep 2, 2025
silverkszlo
left a comment
silverkszlo
left a comment
Contributor
There was a problem hiding this comment.
nice, seems to work in Firefox and Chromium!
Signed-off-by: Enjeck C <patrathewhiz@gmail.com>
Signed-off-by: Enjeck C <patrathewhiz@gmail.com>
enjeck
force-pushed
the
fix-tiptapmenu
branch
from
September 3, 2025 06:21
9239297 to
d30d96c
Compare
github-project-automation
Bot
moved this from 馃Л Planning evaluation (don't pick)
to 鈽戯笍 Done
in 馃摑 Productivity team
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the headings and the rendering of the Tiptap editor. Having the styles in a "scoped" doesn't work. It's okay to leave it unscoped since we give a unique (hopefully) classname, and so shouldn't leak and affect other apps.
Before
After